explicitly mention compile-time options of logging crates for code-size reduction #302
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I found it possible to shave more than 1% off my already optimized .wasm size by using the
release_max_level_off
feature on thetracing
crate. Hence, I suggest to extend the section that already mentions string formatting as a potential vector for code size reduction to point to these features, sincetracing
andlog
are commonly used (also indirectly in dependencies –bevy
in my case).