The book recommends using debug=true so that symbol information will be available in stack traces, however debug=1 seems to be sufficient for informative stack traces.
Why does it not make sense?
I'm working on a project where the intermediate WASM file passed from rustc to wasm-pack is 3.3GB with debug=true. With debug=1, the same file is 0.5GB. This difference corresponds to more than a factor of 2 difference in build times in a common incremental case.
How could we improve it?
Recommend debug=1; or if the extra data produced by debug=true is useful in some way, mention the difference.
Where in the docs did you come across this?
https://rustwasm.github.io/book/reference/debugging.html#building-with-debug-symbols
Describe what about it does not make sense
The book recommends using
debug=trueso that symbol information will be available in stack traces, howeverdebug=1seems to be sufficient for informative stack traces.Why does it not make sense?
I'm working on a project where the intermediate WASM file passed from
rustctowasm-packis 3.3GB withdebug=true. Withdebug=1, the same file is 0.5GB. This difference corresponds to more than a factor of 2 difference in build times in a common incremental case.How could we improve it?
Recommend
debug=1; or if the extra data produced bydebug=trueis useful in some way, mention the difference.