rust/src/test/ui/span/macro-span-replacement.stderr, branch 1.63.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.63.0 2022-06-19T09:32:56+00:00 collapse dead code warnings into a single diagnostic 2022-06-19T09:32:56+00:00 Takayuki Maeda takoyaki0316@gmail.com 2022-06-10T03:14:24+00:00 urn:sha1:3a023e7e589c469c2c761c73eeab9c238818e94b add comments in `store_dead_field_or_variant` support multiple log level add a item ident label fix ui tests fix a ui test fix a rustdoc ui test use let chain refactor: remove `store_dead_field_or_variant` fix a tiny bug Bless tests 2021-10-15T07:36:58+00:00 Cameron Steffen cam.steffen94@gmail.com 2021-10-14T18:28:28+00:00 urn:sha1:90f4521cfdfc85fc04759cfba2f86a6acc096cb3 Show macro name in 'this error originates in macro' message 2021-05-12T23:03:06+00:00 Aaron Hill aa1ronham@gmail.com 2021-02-13T19:52:25+00:00 urn:sha1:0dd9f118d973bb077c6ff0e2a57421ca2eecb81c When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. rustc: Add a warning count upon completion 2020-04-11T14:15:24+00:00 RoccoDev roccodev.business@gmail.com 2020-03-11T15:30:09+00:00 urn:sha1:b85c64c3ea147cadc6014fdea710718a8a153b6b rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros. 2020-02-06T19:46:38+00:00 Eduard-Mihai Burtescu edy.burt@gmail.com 2019-12-16T13:56:47+00:00 urn:sha1:4c7eb59e8161fd7bd2da89fc8c8d73c32bcd789b Normalise notes with the/is 2020-01-24T16:24:50+00:00 varkor github@varkor.com 2020-01-22T23:57:38+00:00 urn:sha1:24a2929ed1d3e1760bf89c878352448fb5ee2087 normalize use of backticks in compiler messages for librustc/lint 2019-07-17T20:49:48+00:00 Samy Kacimi samy.kacimi@protonmail.ch 2019-07-16T20:17:38+00:00 urn:sha1:e5e1397adb755761393bc8e23671d0259a381d16 https://github.com/rust-lang/rust/issues/60532 Update tests 2019-03-11T20:10:26+00:00 Vadim Petrochenkov vadim.petrochenkov@gmail.com 2019-03-09T12:03:44+00:00 urn:sha1:fa72a81bea27f1fda4287475e4cc2f684c971e7f 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 dead-code lint: say "constructed" for structs 2018-07-22T01:30:33+00:00 Zack M. Davis code@zackmdavis.net 2018-07-22T00:55:34+00:00 urn:sha1:6c50ee5abc1f41aaf587f74cc317819ff8eca7d8 This is a sequel to November 2017's #46103 / 1a9dc2e9. It had been reported (more than once—at least #19140, #44083, and #44565) that the "never used" language was confusing for enum variants that were "used" as match patterns, so the wording was changed to say never "constructed" specifically for enum variants. More recently, the same issue was raised for structs (#52325). It seems consistent to say "constructed" here, too, for the same reasons. We considered using more specific word "called" for unused functions and methods (while we declined to do this in #46103, the rationale given in the commit message doesn't actually make sense), but it turns out that Cargo's test suite expects the "never used" message, and maybe we don't care enough even to make a Cargo PR over such a petty and subjective wording change. This resolves #52325.