rust/src/test/ui/impossible_range.rs, branch 1.63.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.63.0 2020-07-02T06:18:33+00:00 Audit uses of `span_suggestion_short` 2020-07-02T06:18:33+00:00 Yuki Okushi huyuumi.dev@gmail.com 2020-07-02T05:32:12+00:00 urn:sha1:ec31b4e3a859c7432232dcdfb559538e0c5a0d5e Ban `...X` pats, harden tests, and improve diagnostics. 2020-01-11T07:58:58+00:00 Mazdak Farrokhzad twingoow@gmail.com 2020-01-11T05:49:43+00:00 urn:sha1:883932c6baf7acd28ab712b80ddeda960f6e37da Also fix a bug with the span passed in `mk_range`. Remove licenses 2018-12-26T04:08:33+00:00 Mark Rousskov mark.simulacrum@gmail.com 2018-12-25T15:56:47+00:00 urn:sha1:2a663555ddf36f6b041445894a8c175cd1bc718c 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`. Do not emit type errors on recovered blocks 2017-12-21T22:57:42+00:00 Esteban Küber esteban@kuber.com.ar 2017-12-14T07:05:49+00:00 urn:sha1:aaf3e318fc33edcc6dbf0920998c3f27d00dd818 When a parse error occurs on a block, the parser will recover and create a block with the statements collected until that point. Now a flag stating that a recovery has been performed in this block is propagated so that the type checker knows that the type of the block (which will be identified as `()`) shouldn't be checked against the expectation to reduce the amount of irrelevant diagnostic errors shown to the user. Remove NOTE/HELP annotations from UI tests 2017-12-14T20:26:39+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2017-12-10T20:29:24+00:00 urn:sha1:1f5b201affc48dcf0b637caa9596c11d83e1db94 Move compile-fail tests with NOTE/HELP annotations to UI 2017-12-14T20:23:07+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2017-12-10T19:47:55+00:00 urn:sha1:d4e51a8fb286444a8c276a05a1c3ba6ba8ca6576