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
Thanks for such a great library! It is really convenient to use in our no-alloc project.
Would it be possible to add a no-color feature flag similarly to colored, that would make the library compile to a no-op and completely disappear in the resulting binary after llvm optimizations? In very constrained environments it would save a lot of Flash memory among others. With this option, the same codebase could be shared between different scales of available resources (like tens of KB Flash to MBs of Flash).
The other benefit is that users of the binary could use the simple interface without having to place if_support_colors everywhere, and then compile-time determine whether the logs should be colorful (e.g. in debug builds) or plain-text (in release).
The text was updated successfully, but these errors were encountered:
I think that's generally true @pacak, but in this case it would be okay because something like this would ideally only be set at the top level. Rhai uses a similar pattern: https://rhai.rs/book/start/features.html
Hi!
Thanks for such a great library! It is really convenient to use in our no-alloc project.
Would it be possible to add a
no-color
feature flag similarly to colored, that would make the library compile to a no-op and completely disappear in the resulting binary after llvm optimizations? In very constrained environments it would save a lot of Flash memory among others. With this option, the same codebase could be shared between different scales of available resources (like tens of KB Flash to MBs of Flash).The other benefit is that users of the binary could use the simple interface without having to place
if_support_colors
everywhere, and then compile-time determine whether the logs should be colorful (e.g. in debug builds) or plain-text (in release).The text was updated successfully, but these errors were encountered: