about summary refs log tree commit diff
path: root/src/test/ui/self
AgeCommit message (Collapse)AuthorLines
2022-03-01update (bless) test resultsFausto-31/+31
2022-02-28Suggest adding a new lifetime parameter when two elided lifetimes should ↵Fausto-0/+186
match up for traits and impls. Issue #94462
2022-02-17Revert "Auto merge of #91403 - cjgillot:inherit-async, r=oli-obk"Oli Scherer-66/+125
This reverts commit 3cfa4def7c87d571bd46d92fed608edf8fad236e, reversing changes made to 5d8767cb229b097fedb1dd4bd9420d463c37774f.
2022-02-12Bless nll tests.Camille GILLOT-3/+2
2022-02-12Inherit lifetimes for async fn instead of duplicating them.Camille GILLOT-122/+64
2022-02-11Revert "Auto merge of #92007 - oli-obk:lazy_tait2, r=nikomatsakis"Oli Scherer-4/+4
This reverts commit e7cc3bddbe0d0e374d05e7003e662bba1742dbae, reversing changes made to 734368a200904ef9c21db86c595dc04263c87be0.
2022-02-02Register member constraints on the final merged hidden typeOli Scherer-6/+7
Previously we did this per hidden type candiate, which didn't always have all the information available.
2022-02-02Lazily resolve type-alias-impl-trait defining usesOli Scherer-8/+7
by using an opaque type obligation to bubble up comparisons between opaque types and other types Also uses proper obligation causes so that the body id works, because out of some reason nll uses body ids for logic instead of just diagnostics.
2022-01-20Rollup merge of #92582 - lcnr:generic-arg-infer, r=BoxyUwUMatthias Krüger-4/+4
improve `_` constants in item signature handling removing the "type" from the error messages does slightly worsen the error messages for types, but figuring out whether the placeholder is for a type or a constant and correctly dealing with that seemed fairly difficult to me so I took the easy way out :sparkles: Imo the error message is still clear enough. r? `@BoxyUwU` cc `@estebank`
2022-01-19Simplify error reporting code, remove await point wordingTyler Mandry-128/+96
2022-01-19NiceRegionError: Use written return type for async fnTyler Mandry-128/+128
2022-01-18generic_arg_infer: placeholder in signature errlcnr-4/+4
2021-12-17Fix typo in "new region bound" suggestionEsteban Kuber-2/+2
The lifetime name shoud always appear in text surrounded by `.
2021-11-14Move some tests to more reasonable directoriesCaio-0/+59
2021-11-06Move some tests to more reasonable directoriesCaio-0/+53
2021-10-18Remove regionck member constraint handling and leave it to mir borrowckOli Scherer-52/+7
2021-10-15simplify constrain_opaque_typesNiko Matsakis-30/+40
2021-09-30Rollup merge of #88838 - FabianWolff:issue-88472, r=estebankManish Goregaokar-3/+4
Do not suggest importing inaccessible items Fixes #88472. For this example: ```rust mod a { struct Foo; } mod b { type Bar = Foo; } ``` rustc currently emits: ``` error[E0412]: cannot find type `Foo` in this scope --> test.rs:6:16 | 6 | type Bar = Foo; | ^^^ not found in this scope | help: consider importing this struct | 6 | use a::Foo; | ``` this is incorrect, as applying this suggestion leads to ``` error[E0603]: struct `Foo` is private --> test.rs:6:12 | 6 | use a::Foo; | ^^^ private struct | note: the struct `Foo` is defined here --> test.rs:2:5 | 2 | struct Foo; | ^^^^^^^^^^^ ``` With my changes, I get: ``` error[E0412]: cannot find type `Foo` in this scope --> test.rs:6:16 | 6 | type Bar = Foo; | ^^^ not found in this scope | = note: this struct exists but is inaccessible: a::Foo ``` As for the wildcard mentioned in #88472, I would argue that the warning is actually correct, since the import _is_ unused. I think the real issue is the wrong suggestion, which I have fixed here.
2021-09-26Improve diagnostics for inaccessible itemsFabian Wolff-2/+5
2021-09-26Do not suggest importing inaccessible itemsFabian Wolff-4/+2
2021-09-26Remove box syntax from most places in src/test outside of the issues direst31-25/+15
2021-09-09Ignore automatically derived impls of `Clone` and `Debug` in dead code analysisFabian Wolff-0/+1
2021-08-30`feature(const_generics)` -> `feature(const_param_types)`lcnr-23/+0
2021-08-11Modify structured suggestion outputEsteban Küber-8/+8
* On suggestions that include deletions, use a diff inspired output format * When suggesting addition, use `+` as underline * Color highlight modified span
2021-07-22bless nll testsOli Scherer-2/+2
2021-07-20Get back the more precise suggestion spans of old regionckOli Scherer-2/+2
2021-07-14Warn about useless assignments of variables/fields to themselvesFabian Wolff-0/+1
2021-06-22Updated tests to reflect specified types in E0121Deadbeef-4/+4
2021-03-29Suggest box/pin/arc ing receiver on method callsEsteban Küber-0/+10
2020-11-10Rollup merge of #76765 - guswynn:async_return, r=tmandryJonas Schievink-96/+128
Make it more clear what an about async fn's returns when referring to what it returns see #76547 This is *likely* not the ONLY place that this happens to be unclear, but we can move this fn to rustc_middle or something like that and reuse it if need be, to apply it to more diagnostics One outstanding question I have is, if the fn returns (), should I make the message more clear (what about `fn f()` vs `fn f() -> ()`, can you tell those apart in the hir?) R? `@tmandry` `@rustbot` modify labels +A-diagnostics +T-compiler
2020-10-20review commentsEsteban Küber-3/+3
2020-10-20Tweak "object unsafe" errorsEsteban Küber-18/+25
Fix #77598.
2020-10-17Make it more clear when complaining about async fn's return typesGus Wynn-96/+128
2020-10-16stabilize union with 'ManuallyDrop' fields and 'impl Drop for Union'Ralf Jung-3/+0
2020-09-02pretty: trim paths of unique symbolsDan Aloni-8/+8
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-07-22Further tweak wording of E0759 and introduce E0767Esteban Küber-4/+4
2020-07-09Reword incorrect `self` token suggestionEsteban Küber-3/+3
2020-06-19Account for multiple impl/dyn Trait in return type when suggesting `'_`Esteban Küber-0/+5
2020-06-15Change E0758 to E0759 to avoid conflict with #72912Esteban Küber-4/+4
2020-06-15small tweaksEsteban Küber-8/+3
2020-06-15Register new eror codeEsteban Küber-0/+2
2020-06-15Use note for requirement source spanEsteban Küber-6/+15
2020-06-15review comments: wordingEsteban Küber-3/+3
2020-06-15Tweak wording and add error codeEsteban Küber-7/+7
2020-06-15Reduce verbosity of suggestion message and mention lifetime in labelEsteban Küber-3/+3
2020-05-30Tweak wording and spans of `'static` `dyn Trait`/`impl Trait` requirementsEsteban Küber-18/+9
2020-05-30review comment: tweak wording and account for span overlapEsteban Küber-2/+2
2020-05-30Account for returned `dyn Trait` evaluating to `'static` lifetimeEsteban Küber-4/+4
Provide a suggestion for `dyn Trait + '_` when possible.
2020-05-07reword "possible candidate" import suggestionAndy Russell-1/+1
2020-03-23Update testsJohn Kåre Alsaker-16/+76
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 13:04:58 +0000