Repository navigation
fix(ir): capture bound catch classes in funs - #64
Merged
Merged
Conversation
mremond
force-pushed
the
fm/task-9e2b9dbd
branch
from
November 16, 2026 07:33
4ffb41f to
187347f
Compare
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
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.
Why
A fun using an outer bound name only as its catch class must match that value instead of catching a mismatching exception.
What changed
Before and after
Before: The reproduction returned wrong natively but right on BEAM; the regression fixture produced six false unused-variable warnings.
After: The reproduction returns right on both runtimes, and the fixture produces zero unused-variable warnings.
This changes compiler diagnostics and generated program behavior, not a graphical view.
Checked
Live validation: Awaiting live validation. This version and evidence need an independent review of coverage and proof.
How it was checked
cargo build --release --locked -p nera-runtime -j 4, then cargo build --release --locked -j 4
cargo clippy --workspace --all-targets --locked -j 4 -- -D warnings
cargo test --workspace --locked --no-fail-fast -j 4: 2226 passed, 0 failed, 1 ignored
python3 scripts/test-allocator-config.py
./target/release/nera test -j 1 --timeout 30: 525 passed, 0 failed, 2 skipped
python3 scripts/test-stacktrace-order.py
cargo test --locked -p nera-ir warnings::unused_vars::tests:: and the new native/BEAM fixture: 10 consecutive passes each
Independent code and retained-proof review passed.
Risk
Risk: low in every dimension.
Full risk assessment
Not done
Windows execution was not run locally; hosted checks cover the configured Linux and macOS jobs.