Document inclusive ranges.#215
Conversation
matthewjasper
left a comment
matthewjasper
left a comment
There was a problem hiding this comment.
One nit. The ... operator in the precedence table (expressions.md) also needs to be changed to ..=. Otherwise LGTM.
Will there be a stabilization PR for this soon?
src/expressions/match-expr.md
Outdated
| ``` | ||
|
|
||
| Other forms of [range] \(`..` for an exclusive range, or any range with one or | ||
| both endpoints left unspecified) are not currently supported in matches. |
There was a problem hiding this comment.
I don't think that 'currently' is needed, the reference only talks about Rust at this point in time.
There was a problem hiding this comment.
Done. I also remarked that ... is still accepted for backwards compatibility.
|
According to rust-lang/rust#28237, all that's left is docs, so hopefully once all my doc PRs are good it will be ready to go. |
|
Note that the failing build is due to using an un-stabilized feature; it should pass once the feature is stabilized and released. |
Havvy
added
the
S-waiting-on-stabilization
|
|
alercah
force-pushed
the
inclusive-ranges
branch
from
f64fd58 to
547305f
Compare
|
Done. |
steveklabnik
removed
the
S-waiting-on-stabilization
|
This just landed as stable in nightly. Let's restart travis! |
|
🎊 |
4 participants
Provides the reference documentation for rust-lang/rust#28237.