rust-lang/rust
1
0
Fork 0
Code Issues Pull Requests Actions 2 Packages Projects Releases Wiki Activity
Files
359bfa901b9d8eddbed7b88b6716dbb77b7bfb95
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.

47 lines
1.8 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 10:40:56 +03: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-15 01:40:08 +00:00
--> $DIR/not-an-allocator.rs:2:11
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 11:13:50 -07:00
LL | #[global_allocator]
mbe: In error messages, don't assume attributes are always proc macros Now that `macro_rules` macros can define attribute rules, make sure error messages account for that.
2025-07-28 03:00:24 -07:00
| ------------------- in this attribute macro expansion
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
LL | static A: usize = 0;
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-15 01:40:08 +00:00
| ^^^^^ the trait `GlobalAlloc` is not implemented for `usize`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 20:56:40 +00:00
= help: the trait `GlobalAlloc` is implemented for `System`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 10:40:56 +03: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-15 01:40:08 +00:00
--> $DIR/not-an-allocator.rs:2:11
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 11:13:50 -07:00
LL | #[global_allocator]
mbe: In error messages, don't assume attributes are always proc macros Now that `macro_rules` macros can define attribute rules, make sure error messages account for that.
2025-07-28 03:00:24 -07:00
| ------------------- in this attribute macro expansion
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
LL | static A: usize = 0;
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-15 01:40:08 +00:00
| ^^^^^ the trait `GlobalAlloc` is not implemented for `usize`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 20:56:40 +00:00
= help: the trait `GlobalAlloc` is implemented for `System`
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 10:40:56 +03: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-15 01:40:08 +00:00
--> $DIR/not-an-allocator.rs:2:11
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 11:13:50 -07:00
LL | #[global_allocator]
mbe: In error messages, don't assume attributes are always proc macros Now that `macro_rules` macros can define attribute rules, make sure error messages account for that.
2025-07-28 03:00:24 -07:00
| ------------------- in this attribute macro expansion
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
LL | static A: usize = 0;
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-15 01:40:08 +00:00
| ^^^^^ the trait `GlobalAlloc` is not implemented for `usize`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 20:56:40 +00:00
= help: the trait `GlobalAlloc` is implemented for `System`
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 10:40:56 +03: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-15 01:40:08 +00:00
--> $DIR/not-an-allocator.rs:2:11
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 11:13:50 -07:00
LL | #[global_allocator]
mbe: In error messages, don't assume attributes are always proc macros Now that `macro_rules` macros can define attribute rules, make sure error messages account for that.
2025-07-28 03:00:24 -07:00
| ------------------- in this attribute macro expansion
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
LL | static A: usize = 0;
Point at type when a `static` `#[global_allocator]` doesn't `impl` `GlobalAlloc`
2021-12-15 01:40:08 +00:00
| ^^^^^ the trait `GlobalAlloc` is not implemented for `usize`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 20:56:40 +00:00
= help: the trait `GlobalAlloc` is implemented for `System`
Add a note to duplicate diagnostics
2023-10-04 18:34:50 +00:00
= note: duplicate diagnostic emitted due to `-Z deduplicate-diagnostics=no`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
error: aborting due to 4 previous errors
For more information about this error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink