about summary refs log tree commit diff
path: root/src/test/ui/on-unimplemented
AgeCommit message (Collapse)AuthorLines
2023-01-11Move /src/test to /testsAlbert Larsan-761/+0
2022-12-13Avoid rendering empty annotationsOli Scherer-6/+0
2022-12-13Make some diagnostics not depend on the source of what they reference being ↵Oli Scherer-6/+6
available
2022-12-11Point at method call when it is the source of the bound errorEsteban Küber-8/+4
2022-12-11Use `with_forced_trimmed_paths`Esteban Küber-2/+2
2022-12-11fix rebaseEsteban Küber-0/+14
2022-12-10fix rebaseEsteban Küber-2/+2
2022-12-08Add `rustc_on_unimplemented` to `Sum` and `Product` trait.Nixon Enraght-Moony-0/+48
2022-11-08Visit attributes of trait impl items during AST validationLeón Orell Valerian Liehr-0/+23
2022-09-04Address nits, rename enclosing_scope => parent_labelMichael Goulet-43/+43
2022-09-04Use head span for rustc_on_unimplemented's enclosing_scope attrMichael Goulet-43/+26
2022-08-27Revert "Remove deferred sized checks"Michael Goulet-4/+96
This reverts commit 33212bf7f527798a8cfa2bbb38781742f4ca718a.
2022-08-21Deduplicate errors that come from places like normalization, sizedMichael Goulet-44/+2
2022-08-21Prefer non-Self non-method types over Self, firstMichael Goulet-8/+8
2022-08-21Rework point-at-argMichael Goulet-2/+44
2022-08-18Reword "Required because of the requirements on the impl of ..."Andy Wang-2/+2
2022-08-16Remove deferred sized checksMichael Goulet-50/+4
2022-07-24suggest dereferencing index when trying to use a reference of usize as indexTakayuki Maeda-4/+4
2022-07-19Mention first and last macro in backtraceMichael Goulet-4/+4
2022-04-05Rollup merge of #95525 - ohno418:suggest-derivable-trait-E0277, ↵Dylan DPC-0/+4
r=compiler-errors Suggest derivable trait on E0277 error Closes https://github.com/rust-lang/rust/issues/95099 .
2022-04-05Suggest derivable trait on E0277ohno418-0/+4
2022-04-04Refer to the TraitRef::identity in the message to be clearerEsteban Kuber-7/+7
2022-04-04Dedup logic and improve output for other types that impl traitEsteban Kuber-7/+7
2022-04-04Mention implementers of unsatisfied traitEsteban Kuber-0/+25
When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that *do* implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 | LL | impl Baz<f32> for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz<U: ?Sized> where U: Foo { } | ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`.
2022-03-06allow referencing impl substs from rustc_on_unimplementedMichael Goulet-0/+28
2021-11-20Do not mention associated items when they introduce an obligationEsteban Kuber-20/+0
2021-10-24Always sort suggestions before emitting themEsteban Kuber-2/+2
2021-09-16Point at call span that introduced obligation for the argEsteban Kuber-8/+24
2021-08-16Use note to point at bound introducing requirementEsteban Küber-18/+34
2021-07-19Various diagnostics clean ups/tweaksEsteban Küber-12/+20
* Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition
2021-06-22Change Debug unimplemented message per requestAris Merchant-1/+1
2021-06-16Update test stderr filesAris Merchant-5/+1
2021-05-12Show macro name in 'this error originates in macro' messageAaron Hill-4/+4
When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2020-09-02pretty: trim paths of unique symbolsDan Aloni-23/+23
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-08Small tweaks to required bound spanEsteban Küber-6/+6
2020-03-01Make `rustc_attrs` tracking issue NoneYuki Okushi-1/+0
2020-02-09--bless --compare-mode=nllMatthias Prechtl-1/+1
2020-02-06rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.Eduard-Mihai Burtescu-0/+4
2019-12-06parse_meta: ditch parse_in_attrMazdak Farrokhzad-6/+3
2019-12-03Rollup merge of #66651 - Areredify:on-unimplemented-scope, r=davidtwcoMazdak Farrokhzad-0/+93
Add `enclosing scope` parameter to `rustc_on_unimplemented` Adds a new parameter to `#[rustc_on_unimplemented]`, `enclosing scope`, which highlights the function or closure scope with a message. The wip part refers to adding this annotation to `Try` trait to improve ergonomics (which I don't know how to do since I change both std and librustc) Closes #61709.
2019-11-26Refactor 'parse_enum_item' to use 'parse_delim_comma_seq'Janusz Marcinkiewicz-1/+4
2019-11-25add `enclosing_scope` param to `rustc_on_unimplmented`Mikhail Babenko-0/+93
add ui test compute enclosing_scope_span on demand add scope test make tidy happy stylistic and typo fixes
2019-11-08Rollup merge of #66007 - estebank:remove-here, r=CentrilMazdak Farrokhzad-1/+1
Remove "here" from "expected one of X here"
2019-11-06Remove "here" from "expected one of X here"Esteban Küber-1/+1
2019-11-06gate rustc_on_unimplemented under rustc_attrsMazdak Farrokhzad-5/+25
2019-10-24Increase spacing for suggestions in diagnosticsEsteban Küber-0/+1
Make the spacing between the code snippet and verbose structured suggestions consistent with note and help messages.
2019-09-22On obligation errors point at the unfulfilled binding when possibleEsteban Küber-2/+2
2019-09-19When possible point at argument causing item obligation failureEsteban Küber-26/+26
2019-08-31Use span label instead of note for cause in E0631Esteban Küber-30/+18
2019-05-25Reword malformed attribute input diagnosticsEsteban Küber-2/+8
- Handle empty `cfg_attr` attribute - Reword empty `derive` attribute error - Use consistend error message: "malformed `attrname` attribute input" - Provide suggestions when possible - Move note/help to label/suggestion - Use consistent wording "ill-formed" -> "malformed" - Move diagnostic logic out of parser