mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
674a3d5c1c
rust/tests/ui/allocator/not-an-allocator.stderr

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

48 lines
2.1 KiB
Plaintext
Raw Normal View History

pretty: trim paths of unique symbols 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-09-02 02:40:56 -05:00
error[E0277]: the trait bound `usize: GlobalAlloc` is not satisfied
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-14 19:40:08 -06:00
--> $DIR/not-an-allocator.rs:2:11
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Various diagnostics clean ups/tweaks * 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-07-17 13:13:50 -05:00
LL | #[global_allocator]
| ------------------- in this procedural macro expansion
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
LL | static A: usize = 0;
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-14 19:40:08 -06:00
| ^^^^^ the trait `GlobalAlloc` is not implemented for `usize`
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Mention implementers of unsatisfied trait 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 `?`.
2021-12-13 14:56:40 -06:00
= help: the trait `GlobalAlloc` is implemented for `System`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the attribute macro `global_allocator` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
pretty: trim paths of unique symbols 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-09-02 02:40:56 -05:00
error[E0277]: the trait bound `usize: GlobalAlloc` is not satisfied
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-14 19:40:08 -06:00
--> $DIR/not-an-allocator.rs:2:11
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Various diagnostics clean ups/tweaks * 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-07-17 13:13:50 -05:00
LL | #[global_allocator]
| ------------------- in this procedural macro expansion
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
LL | static A: usize = 0;
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-14 19:40:08 -06:00
| ^^^^^ the trait `GlobalAlloc` is not implemented for `usize`
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Mention implementers of unsatisfied trait 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 `?`.
2021-12-13 14:56:40 -06:00
= help: the trait `GlobalAlloc` is implemented for `System`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the attribute macro `global_allocator` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
pretty: trim paths of unique symbols 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-09-02 02:40:56 -05:00
error[E0277]: the trait bound `usize: GlobalAlloc` is not satisfied
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-14 19:40:08 -06:00
--> $DIR/not-an-allocator.rs:2:11
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Various diagnostics clean ups/tweaks * 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-07-17 13:13:50 -05:00
LL | #[global_allocator]
| ------------------- in this procedural macro expansion
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
LL | static A: usize = 0;
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-14 19:40:08 -06:00
| ^^^^^ the trait `GlobalAlloc` is not implemented for `usize`
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Mention implementers of unsatisfied trait 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 `?`.
2021-12-13 14:56:40 -06:00
= help: the trait `GlobalAlloc` is implemented for `System`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the attribute macro `global_allocator` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
pretty: trim paths of unique symbols 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-09-02 02:40:56 -05:00
error[E0277]: the trait bound `usize: GlobalAlloc` is not satisfied
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-14 19:40:08 -06:00
--> $DIR/not-an-allocator.rs:2:11
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Various diagnostics clean ups/tweaks * 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-07-17 13:13:50 -05:00
LL | #[global_allocator]
| ------------------- in this procedural macro expansion
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
LL | static A: usize = 0;
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-14 19:40:08 -06:00
| ^^^^^ the trait `GlobalAlloc` is not implemented for `usize`
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Mention implementers of unsatisfied trait 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 `?`.
2021-12-13 14:56:40 -06:00
= help: the trait `GlobalAlloc` is implemented for `System`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error.
2021-02-13 13:52:25 -06:00
= note: this error originates in the attribute macro `global_allocator` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
error: aborting due to 4 previous errors
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink