mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2b2c0f9886
rust/tests/ui/box/unit/unique-pinned-nocopy.stderr

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

29 lines
1022 B
Plaintext
Raw Normal View History

Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note.
2020-09-26 16:20:14 -05:00
error[E0599]: the method `clone` exists for struct `Box<R>`, but its trait bounds were not satisfied
tests: remove ignore directives from tests that mention core/alloc/std spans.
2020-03-31 20:10:13 -05:00
--> $DIR/unique-pinned-nocopy.rs:12:16
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Support custom allocators in `Box` Remove `Box::leak_with_alloc` Add leak-test for box with allocator Rename `AllocErr` to `AllocError` in leak-test Add `Box::alloc` and adjust examples to use the new API
2020-10-06 09:37:23 -05:00
LL | struct R {
| -------- doesn't satisfy `R: Clone`
Add more context to E0599 errors Point at the intermediary unfullfilled trait bounds.
2020-02-18 01:22:19 -06:00
...
Support custom allocators in `Box` Remove `Box::leak_with_alloc` Add leak-test for box with allocator Rename `AllocErr` to `AllocError` in leak-test Add `Box::alloc` and adjust examples to use the new API
2020-10-06 09:37:23 -05:00
LL | let _j = i.clone();
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note.
2020-09-26 16:20:14 -05:00
| ^^^^^ method cannot be called on `Box<R>` due to unsatisfied trait bounds
Make some diagnostics not depend on the source of what they reference being available
2022-12-09 09:56:23 -06:00
--> $SRC_DIR/alloc/src/boxed.rs:LL:COL
Avoid rendering empty annotations
2022-12-12 09:25:04 -06:00
::: $SRC_DIR/alloc/src/boxed.rs:LL:COL
|
= note: doesn't satisfy `Box<R>: Clone`
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
|
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note.
2020-09-26 16:20:14 -05:00
= note: the following trait bounds were not satisfied:
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
`R: Clone`
which is required by `Box<R>: Clone`
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
= help: items from traits can only be used if the trait is implemented and in scope
= note: the following trait defines an item `clone`, perhaps you need to implement it:
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
candidate #1: `Clone`
Suggest deriving traits if possible This only applies to builtin derives as I don't think there is a clean way to get the available derives in typeck. Closes #85851
2021-07-26 13:26:23 -05:00
help: consider annotating `R` with `#[derive(Clone)]`
|
Tweak output for 'add line' suggestion
2023-03-17 21:18:39 -05:00
LL + #[derive(Clone)]
LL | struct R {
Suggest deriving traits if possible This only applies to builtin derives as I don't think there is a clean way to get the available derives in typeck. Closes #85851
2021-07-26 13:26:23 -05:00
|
Moved compile-fail tests to ui tests.
2018-08-08 07:28:26 -05:00
error: aborting due to previous error
For more information about this error, try `rustc --explain E0599`.
Reference in New Issue Copy Permalink