# \`...\` vs \`..=\` for inclusive ranges

**URL:** <https://internals.rust-lang.org/t/vs-for-inclusive-ranges/1539>\
**Category:** ideas (deprecated)\
**Created:** [February 4, 2015, 1:23pm UTC](https://internals.rust-lang.org/t/vs-for-inclusive-ranges/1539 "2015-02-04T13:23:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![japaric](https://sea2.discourse-cdn.com/flex002/user_avatar/internals.rust-lang.org/japaric/32/28_2.png) [@japaric](https://internals.rust-lang.org/u/japaric)\
**Post date:** [February 4, 2015, 1:38pm UTC](https://internals.rust-lang.org/t/vs-for-inclusive-ranges/1539/3 "2015-02-04T13:38:01Z")

</div>

+1 for having syntax for inclusive ranges in expressions, instead of using an adaptor `a..b.inclusive()` (which I think is too long for its own good, and people will tend to write `a..b+1` even if it overflows the upper limit).

And `a..=b` looks good IMO, and it’s easy to distinguish it from `a..b` when reading code.

---

_[View the full topic](https://internals.rust-lang.org/t/vs-for-inclusive-ranges/1539)._
