chore: add package.cargo-near.debug = true
to release profile
#195
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.
it was noticed that default suggestions to enable backtrace only produce confusion, as backtrace info
without source code is more confusing than helpful:
current (in main)
RUST_BACKTRACE=1 cargo near build
current (in main)
RUST_BACKTRACE=full cargo near build
from this pr
RUST_BACKTRACE=1 cargo near build
from this pr
RUST_BACKTRACE=full cargo near build
this beefs up the binary size twice, doing a plain
debug = true
for release profile results in 250 MB binaryalternative to this is #196