Update for stabilization of the never type - #2283
Merged
Merged
Conversation
ehuss
added
the
S-waiting-on-stabilization
rustbot
added
the
S-waiting-on-review
Comment on lines
-78
to
-79
| > [!EDITION-2024] | ||
| > Before the 2024 edition, the type was inferred to instead be `()`. |
Member
There was a problem hiding this comment.
A shame that we can't represent "before rust x.y.z with edition < 2024"...
Contributor
Author
|
Thanks @WaffleLapkin! |
traviscross
force-pushed
the
stabilize-never
branch
from
June 23, 2026 19:46
46df26b to
7f585d0
Compare
This comment has been minimized.
This comment has been minimized.
traviscross
approved these changes
Jun 23, 2026
traviscross
removed
the
S-waiting-on-review
traviscross
force-pushed
the
stabilize-never
branch
from
June 23, 2026 21:10
7f585d0 to
bfba255
Compare
This was referenced Jul 8, 2026
Stabilizing the never type means making `!` available in all positions and changing the never-to-any coercion fallback type to `!` in older editions. Let's make the updates needed for that.
In various places, we had worked around the never type being unstable when writing examples. Now that it is stable, let's clean those examples up.
This moves type.never.intro to the top of the chapter to match the style where the intro should always come first in a section.
This moves the never example to the intro to match our layout style, and adds an example showing a type expression using `!`.
Never can coerce to itself.
This tries to punch up the never type intro by linking to the divergence chapter.
traviscross
force-pushed
the
stabilize-never
branch
from
August 25, 2026 19:33
bfba255 to
852079c
Compare
Collaborator
|
This PR was rebased onto a different master commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
traviscross
approved these changes
Aug 25, 2026
Contributor
|
Thanks @WaffleLapkin; thanks @ehuss. |
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
4 participants
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.
This updates for the stabilization of the never type proposed in rust-lang/rust#155499.
cc @WaffleLapkin