Skip to content

Say that ... range patterns are rejected in the 2021 edition #1114

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.

Sign up for GitHub

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
merged 2 commits into from
Dec 11, 2021
Merged

Say that ... range patterns are rejected in the 2021 edition #1114

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4725958
Say that `...` range patterns are rejected in the 2021 edition
mattheww Dec 3, 2021
b83fcc1
Make it clearer that `..=` range patterns work in all editions
mattheww Dec 3, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions src/patterns.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -443,8 +443,6 @@ A half-open range pattern in the style `a..` cannot be used to match within the
A pattern `a..=b` must always have a ≤ b. It is an error to have a range pattern
`10..=0`, for example.

The `...` syntax is kept for backwards compatibility.

Range patterns only work on scalar types. The accepted types are:

* Integer types (u8, i8, u16, i16, usize, isize, etc.).
Expand Down Expand Up @@ -535,6 +533,8 @@ minimum to maximum value. The range of values for a `char` type are precisely th
ranges containing all Unicode Scalar Values: `'\u{0000}'..='\u{D7FF}'` and
`'\u{E000}'..='\u{10FFFF}'`.

> **Edition Differences**: Before the 2021 edition, closed range patterns may also be written using `...` as an alternative to `..=`, with the same meaning.

## Reference patterns

> **<sup>Syntax</sup>**\
Expand Down