about summary refs log tree commit diff
path: root/src/test/ui/missing/missing-items
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-197/+0
2022-06-16 fix one more case of trailing spaceklensy-1/+1
2022-06-02add new `emit_inference_failure_err`lcnr-5/+4
2022-05-20report ambiguous type parameters when their parents are impl or fnTakayuki Maeda-0/+6
fix ci error emit err for `impl_item`
2022-04-04diagnostics: use correct span for const genericsMichael Howell-2/+2
Fixes #95616
2021-12-10bless testsEllen-8/+8
2021-12-10update testsEllen-3/+0
2021-08-11Modify structured suggestion outputEsteban Küber-12/+12
* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-05-07Fix impl type parameter suggestion involving constsmibac138-9/+49
2021-05-06Expand impl type parameter suggestion testsmibac138-0/+103
2020-11-19Regroup many usefulness-related test in the same folderNadrieril-34/+0
2020-09-02pretty: trim paths of unique symbolsDan Aloni-4/+4
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.
2020-04-16Fixed issue with self: &Box<Self>Duddino-2/+4
2020-04-16fixed missing trait method suggests incorrect code (self parameter not named ↵Duddino-2/+8
self)
2020-03-27non-exhastive diagnostic: add note re. scrutinee typeMazdak Farrokhzad-0/+1
2020-02-08review commentEsteban Küber-1/+1
2019-12-14Indicate origin of where type parameter for uninferred typesOhad Ravid-1/+1
2019-12-11Add more context for type parametersEsteban Küber-1/+1
2019-11-06Suggest missing item from `trait` in `impl`Esteban Küber-3/+3
2019-03-11Update testsVadim Petrochenkov-3/+3
2019-03-02Point at enum definition when match patterns are not exhaustiveEsteban Küber-2/+10
``` error[E0004]: non-exhaustive patterns: type `X` is non-empty --> file.rs:9:11 | 1 | / enum X { 2 | | A, | | - variant not covered 3 | | B, | | - variant not covered 4 | | C, | | - variant not covered 5 | | } | |_- `X` defined here ... 9 | match x { | ^ | = help: ensure that all possible cases are being handled, possibly by adding wildcards or more match arms error[E0004]: non-exhaustive patterns: `B` and `C` not covered --> file.rs:11:11 | 1 | / enum X { 2 | | A, 3 | | B, 4 | | C, | | - not covered 5 | | } | |_- `X` defined here ... 11 | match x { | ^ patterns `C` not covered ``` When a match expression doesn't have patterns covering every variant, point at the enum's definition span. On a best effort basis, point at the variant(s) that are missing. This does not handle the case when the missing pattern is due to a field's enum variants: ``` enum E1 { A, B, C, } enum E2 { A(E1), B, } fn foo() { match E2::A(E1::A) { E2::A(E1::B) => {} E2::B => {} } //~^ ERROR `E2::A(E1::A)` and `E2::A(E1::C)` not handled } ``` Unify look between match with no arms and match with some missing patterns. Fix #37518.
2018-12-25Remove licensesMark Rousskov-44/+3
2018-08-14Merged migrated compile-fail tests and ui tests. Fixes #46841.David Wood-0/+110