rust/src/test/parse-fail/range_inclusive.rs, branch 1.26.2 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.26.2 2018-03-15T08:58:02+00:00 Stabilize `inclusive_range_syntax` language feature. 2018-03-15T08:58:02+00:00 kennytm kennytm@gmail.com 2018-01-27T19:19:29+00:00 urn:sha1:92d1f8d8e4be62e6f4dc32bc57f9d44f53117ec9 Stabilize the syntax `a..=b` and `..=b`. Stabilize `inclusive_range` library feature. 2018-03-15T08:58:01+00:00 kennytm kennytm@gmail.com 2018-01-27T19:09:36+00:00 urn:sha1:b5913f2e7695ad247078619bf4c6a6d3dc4dece5 Stabilize std::ops::RangeInclusive and std::ops::RangeInclusiveTo. Add support for `..=` syntax 2017-09-22T20:05:18+00:00 Alex Burka alex@alexburka.com 2017-09-19T05:40:04+00:00 urn:sha1:e64efc91f49affb265328e354c8c8f0544daa462 Add ..= to the parser Add ..= to libproc_macro Add ..= to ICH Highlight ..= in rustdoc Update impl Debug for RangeInclusive to ..= Replace `...` to `..=` in range docs Make the dotdoteq warning point to the ... Add warning for ... in expressions Updated more tests to the ..= syntax Updated even more tests to the ..= syntax Updated the inclusive_range entry in unstable book address nits 2016-03-24T05:42:23+00:00 Alex Burka aburka@seas.upenn.edu 2016-03-18T23:04:43+00:00 urn:sha1:861644f2af5421f5aa55d4e7fddfc8dba54bcb70 fatal error instead of ICE for impossible range during HIR lowering 2016-03-24T05:33:31+00:00 Alex Burka aburka@seas.upenn.edu 2016-03-15T17:03:42+00:00 urn:sha1:9799cacba3042420cc7b49d555289241cf0456e1 End-less ranges (`a...`) don't parse but bad syntax extensions could conceivably produce them. Unbounded ranges (`...`) do parse and are caught here. The other panics in HIR lowering are all for unexpanded macros, which cannot be constructed by bad syntax extensions. test inclusive ranges 2016-02-27T07:01:41+00:00 Alex Burka aburka@seas.upenn.edu 2016-01-13T06:28:29+00:00 urn:sha1:69719df6116b584b71ee5a8d22974835c33b13be Mostly copy the tests from half-open ranges, adding some more for DoubleEndedIterator and ExactSizeIterator. Also thoroughly (I think) test that the feature gates are working.