You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In libcnb I used BuildpackOutput because that's what it literally was. When I generalized the name, I introduced a conflict:
Output conflicts with std::process::Output
One of the expectations is that people will use this in conjunction with std::process::Command a bunch, therefore conflicting with std::prcesss::Output isn't great out of the gate.
Alternatives:
Stream conflicts with some other std structs
Log is the wrong mental model (because people think logs are not seen by people)
Cli isn't the right frame as people expect that to be interactive
When trying to use both `std::process::Output` and `bullet_stream::Output` in the same file there is an import collision.
With this change the `Print` struct is introduced. The `Output` struct is still available but is deprecated.
Close#4
When trying to use both `std::process::Output` and `bullet_stream::Output` in the same file there is an import collision.
With this change the `Print` struct is introduced. The `Output` struct is still available but is deprecated.
Close#4
In libcnb I used
BuildpackOutput
because that's what it literally was. When I generalized the name, I introduced a conflict:Output
conflicts withstd::process::Output
One of the expectations is that people will use this in conjunction with
std::process::Command
a bunch, therefore conflicting withstd::prcesss::Output
isn't great out of the gate.Alternatives:
Stream
conflicts with some other std structsLog
is the wrong mental model (because people think logs are not seen by people)Cli
isn't the right frame as people expect that to be interactiveTui
is not a commonly known term and the people who do know it would also expect it to be interactive https://github.com/ratatui-org/ratatuiOut
feels TOO generalText
no known conflicts.Text<SubBullet>
isn't horrible. It is what it is, except that it's text printed to the user, not written to retrieve laterPrint
no known conflicts.Print<SubBullet>
is also not horrible. I think it's closer thanText
.The text was updated successfully, but these errors were encountered: