rust/src/test/ui/allocator/not-an-allocator.stderr, branch 1.63.0

Mention implementers of unsatisfied trait

2022-04-04T21:01:42+00:00

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 for f32 { } | ^^^^^^^^ the trait `Foo` is not implemented for `f32` | = help: the following other types implement trait `Foo`: Option i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 | LL | trait Baz 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 `?`.

Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`

2021-12-15T01:40:08+00:00

Do not mention associated items when they introduce an obligation

2021-11-20T19:19:31+00:00

Various diagnostics clean ups/tweaks

2021-07-19T15:43:35+00:00

* Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition

Show macro name in 'this error originates in macro' message

2021-05-12T23:03:06+00:00

When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.

pretty: trim paths of unique symbols

2020-09-02T19:26:37+00:00

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.

rustc_macros: don't limit the -Zmacro-backtrace suggestion to extern macros.

2020-02-06T19:46:38+00:00

Remove licenses

2018-12-26T04:08:33+00:00

Merged migrated compile-fail tests and ui tests. Fixes #46841.

2018-08-14T09:12:09+00:00