rust/src/test/ui/pattern/usefulness/refutable-pattern-errors.stderr, branch 1.60.0 https://github.com/rust-lang/rust http://git.dreamy.place/mirrors/rust/atom?h=1.60.0 2021-04-03T20:30:20+00:00 Remove redundant `ignore-tidy-linelength` annotations 2021-04-03T20:30:20+00:00 Simon Jakobi simon.jakobi@gmail.com 2021-04-03T11:05:11+00:00 urn:sha1:3ea62cb5d19846b44172d861ae231c8c09322800 This is step 2 towards fixing #77548. In the codegen and codegen-units test suites, the `//` comment markers were kept in order not to affect any source locations. This is because these tests cannot be automatically `--bless`ed. pretty: trim paths of unique symbols 2020-09-02T19:26:37+00:00 Dan Aloni alonid@gmail.com 2020-09-02T07:40:56+00:00 urn:sha1:07e7823c01be1733df2480de19fbbe6b8e9384cf If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. Show the values and computation that would overflow a const evaluation or propagation 2020-06-26T08:08:52+00:00 Oliver Scherer github35764891676564198441@oli-obk.de 2020-06-19T16:57:15+00:00 urn:sha1:819cde5dabd90dab1fb462cd713457421d0ebd36 Prefer the associated consts for pattern matching error 2020-06-13T01:18:18+00:00 Lzu Tao taolzu@gmail.com 2020-06-11T03:03:59+00:00 urn:sha1:c755292859546105b06ffa2936c0def095763e03 non-exhastive diagnostic: add note re. scrutinee type 2020-03-27T05:49:07+00:00 Mazdak Farrokhzad twingoow@gmail.com 2020-03-27T05:44:30+00:00 urn:sha1:c858593ed013127ab35c7d5777156fe9f24a3717 Gather together usefulness tests 2019-10-27T21:20:26+00:00 Nadrieril nadrieril@gmail.com 2019-09-28T14:05:38+00:00 urn:sha1:09f9947ebc68a8199c3dff8607a41571c48cc377 I took most tests that were testing only for match exhaustiveness, pattern refutability or match arm reachability, and put them in the same test folder.