### Current status We are planning to to change the syntax for inclusive ranges and patterns to `..=`. The `...` syntax in patterns is stable and will remain (silently) deprecated for the time being; rustfmt can rewrite `...` to `..=`. This comes after much discussion. [See this comment for justification.](https://github.com/rust-lang/rust/issues/28237#issuecomment-304145654) **No more syntax discussion should be had in this thread**. Any different proposals of exclusive range syntax should take place on the [user's forum](https://users.rust-lang.org/) or [internals forum](https://internals.rust-lang.org/), **after** you have read all existing comments and their rationale here. Notably, breaking backwards compatibility is a non-starter. ### Steps to take * [x] Initial implementation * [x] Change to accept `..=` as synonym for `...` in patterns and to accept `..=` in expressions #44709 - [Initial mentoring instructions on writing the PR can be found here.](https://github.com/rust-lang/rust/issues/28237#issuecomment-304308234) * [x] Documentation * [x] Book rust-lang/book#1134 * [x] Reference rust-lang-nursery/reference#215 * [x] Rust-by-example rust-lang/rust-by-example#1015 * [x] https://github.com/rust-lang/rfcs/pull/1980 proposed a tweak to `RangeInclusive` * [x] Stabilization #47813 * Note: The fields of `RangeInclusive` have been left out from this round of stabilization. Please track #49022 on this feature.
