Conversation
…well as improvements to error handling
Brings the v0.8.1 (#220) release commit from master into develop. Conflicts in the release-bookkeeping files (dotscope/Cargo.toml, dotscope-cli/Cargo.toml, Cargo.lock, README.md, CHANGELOG.md) resolved in favour of develop, which already carries the newer 0.8.2 state (version bump, 0.8.2 changelog entry, #218 fat-header fix + regression test, and the docs.rs ci.yml fix). Master contributed no unique content.
Backmerge the v0.8.1 (#220) release commit from master so develop contains it as an ancestor, unblocking the v0.8.2 develop->master PR. Release-bookkeeping conflicts (dotscope/Cargo.toml, dotscope-cli/Cargo.toml, Cargo.lock, README.md, CHANGELOG.md) resolved in favour of develop's newer 0.8.2 state. Master contributed no unique source content.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixed
encode_exception_handlersemitted the fat exception-handling section header as 6 bytes (Kind+ 2 reserved bytes +DataSize) instead of the 4 bytes mandated by ECMA-335 §II.25.4.5 (Kind(1 byte) +DataSize(3 bytes)). The two extra bytes shifted theDataSizefield, so a method written back to disk reported a garbage handler count (e.g.0x1C0000 / 24 = 76458) and downstream runtimes (Mono/IKVM) crashed resolving a bogus catch-type token. The header is now exactly 4 bytes and survives a write/parse round-tripChanged
num-bigint(0.4.6 → 0.5.0),z3(0.20.1 → 0.20.2),quick-xml(0.40.1 → 0.41.0),memmap2(0.9.10 → 0.9.11),rustc-hash(2.1.2 → 2.1.3), andenv_logger(0.11.10 → 0.11.11)