colored only offers ColoredStrings i.e. owned head-allocated strings which is very wasteful especially since we use a lot of colored string literals
I am not in the mood to fork the library and add a ColoredStr<'_>
I actually don't like the API anymore, the extension methods, as it leads to quite verbose and boilerplate-y code (nested format!s etc.)
Blockers
Issue #21: I'd like to support "runtime"/dynamic color specifications since I don't want to speckle my code with hard-coded colors but I'd like to define color constants with semantic naming (see the diagnostics code)
Open Questions
How does it deal with the NO_COLOR environment variable?
Motivation
colored
only offersColoredString
s i.e. owned head-allocated strings which is very wasteful especially since we use a lot of colored string literalsColoredStr<'_>
format!
s etc.)Blockers
Open Questions
NO_COLOR
environment variable?