Add documentation warnings for Rust, Go, and JavaScript #234
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.
3 main changes:
--release
warning in the Rust docs to clarify that always building with--release
might not be ideal if you're prototyping/testing locally and you need debug info in your backtraces-no-debug
warning in the Go docs to clarify that by default tinygo includes all debug information and that you can optimize your .wasm file by using-no-debug
(up to 75% reduction in size)--disable all
warning in the JS docs since many users might actually need to useconsole.log
ornew Date()
in their component for logging/debugging