fix: Fix decommitment cost divergence #57
Merged
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.
What ❔
Fixes decommitment cost divergence introduced after fixing the previous VM divergence.
Why ❔
As of now, bytecode decommitment cost is now not charged even if decommitment failed; this is incorrect. The easiest fix implemented in this PR is to track decommitment status (successful / failed) for all bytecodes.
Checklist
cargo fmt
andcargo clippy
.