rust/src/test/ui/lint/inclusive-range-pattern-syntax.fixed, branch 1.52.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.52.0 2020-01-23T00:00:00+00:00 Use check-pass mode for lint tests 2020-01-23T00:00:00+00:00 Tomasz Miąsko tomasz.miasko@gmail.com 2020-01-23T00:00:00+00:00 urn:sha1:d915c016c986d3060d6275f472b8a6e4c22b56ea Migrate compile-pass annotations to build-pass 2019-07-02T21:30:28+00:00 Yuki Okushi huyuumi.dev@gmail.com 2019-07-02T21:30:28+00:00 urn:sha1:c004451a209dce4960fc295ff799e17f2630a00c 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 Rewrite `...` as `..=` as a MachineApplicable 2018 idiom lint 2018-11-10T19:26:49+00:00 varkor github@varkor.com 2018-11-10T18:08:50+00:00 urn:sha1:c1487145493c54b41df16eb7ffe6fdd3b82e6a78 inclusive range syntax lint (`...` → `..=`) 2018-06-26T14:54:49+00:00 Zack M. Davis code@zackmdavis.net 2018-05-29T02:32:03+00:00 urn:sha1:3fb76f4027596f524403e6eea60e9531e70e9460 Our implementation ends up changing the `PatKind::Range` variant in the AST to take a `Spanned<RangeEnd>` instead of just a `RangeEnd`, because the alternative would be to try to infer the span of the range operator from the spans of the start and end subexpressions, which is both hideous and nontrivial to get right (whereas getting the change to the AST right was a simple game of type tennis). This is concerning #51043.