-
-
Notifications
You must be signed in to change notification settings - Fork 14.4k
Add test for never type fallback in try blocks with Into<!>
#150434
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
bors
merged 1 commit into
rust-lang:main
from
AprilNEA:test-125364-never-type-try-blocks
Dec 28, 2025
Merged
Add test for never type fallback in try blocks with Into<!>
#150434
bors
merged 1 commit into
rust-lang:main
from
AprilNEA:test-125364-never-type-try-blocks
Dec 28, 2025
Conversation
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
Closes rust-lang#125364 This test verifies that the never type fallback behavior in try blocks with `Into<!>` bounds works correctly across different editions: - Edition 2021: Fallback to `()` causes type error - Edition 2024: Fallback to `!` compiles successfully
Collaborator
|
r? @davidtwco rustbot has assigned @davidtwco. Use |
Collaborator
|
Contributor
Author
WaffleLapkin
approved these changes
Dec 27, 2025
Member
|
@bors r+ rollup |
Collaborator
rust-timer
added a commit
that referenced
this pull request
Dec 28, 2025
Rollup merge of #150434 - AprilNEA:test-125364-never-type-try-blocks, r=WaffleLapkin Add test for never type fallback in try blocks with `Into<!>` ### Summary Adds UI tests for issue #125364, which involves the interaction between never type fallback, try blocks, and `From`/`Into` trait bounds. ### Changes - Added `tests/ui/never_type/try-block-never-type-fallback.rs` - Tests both edition 2021 (where the issue manifests) and edition 2024 (where it's fixed) ### Issue Closes #125364 ### Testing ```bash ./x test tests/ui/never_type/try-block-never-type-fallback.rs ``` Both test variants pass: e2021: Correctly fails with expected error e2024: Compiles successfully (check-pass) ### Notes This test documents the edition-dependent behavior of never type fallback in try blocks, as requested in the original issue. cc `@WaffleLapkin`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
S-waiting-on-bors
Status: Waiting on bors to run and complete tests. Bors will change the label on completion.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
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.
Summary
Adds UI tests for issue #125364, which involves the interaction between
never type fallback, try blocks, and
From/Intotrait bounds.Changes
tests/ui/never_type/try-block-never-type-fallback.rsIssue
Closes #125364
Testing
./x test tests/ui/never_type/try-block-never-type-fallback.rsBoth test variants pass:
e2021: Correctly fails with expected error
e2024: Compiles successfully (check-pass)
Notes
This test documents the edition-dependent behavior of never type fallback in try blocks, as requested in the original issue.
cc @WaffleLapkin