mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
rust/src/test/ui/union/union-derive-clone.stderr

37 lines
1.3 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 `U1: Copy` is not satisfied
stabilize union with 'ManuallyDrop' fields and 'impl Drop for Union'
2020-10-04 22:24:14 +02:00
--> $DIR/union-derive-clone.rs:3:10
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
|
Update tests
2019-03-09 15:03:44 +03:00
LL | #[derive(Clone)]
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
| ^^^^^ the trait `Copy` is not implemented for `U1`
Use `PredicateObligation`s instead of `Predicate`s Keep more information about trait binding failures.
2020-03-03 15:07:04 -08:00
|
mv std libs to library/
2020-06-11 21:31:49 -05:00
::: $SRC_DIR/core/src/clone.rs:LL:COL
Use `PredicateObligation`s instead of `Predicate`s Keep more information about trait binding failures.
2020-03-03 15:07:04 -08:00
|
LL | pub struct AssertParamIsCopy<T: Copy + ?Sized> {
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
| ---- required by this bound in `AssertParamIsCopy`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
|
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 14:52:25 -05:00
= note: this error originates in the derive macro `Clone` (in Nightly builds, run with -Z macro-backtrace for more info)
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 17:20:14 -04:00
error[E0599]: the method `clone` exists for union `U5<CloneNoCopy>`, but its trait bounds were not satisfied
stabilize union with 'ManuallyDrop' fields and 'impl Drop for Union'
2020-10-04 22:24:14 +02:00
--> $DIR/union-derive-clone.rs:35:15
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
|
Change untagged_unions to not allow union fields with drop Union fields may now never have a type with attached destructor. This for example allows unions to use arbitrary field types only by wrapping them in ManuallyDrop. The stable rule remains, that union fields must be Copy. We use the new rule for the `untagged_union` feature. See RFC 2514. Note for ui tests: We can't test move out through Box's deref-move since we can't have a Box in a union anymore.
2018-12-19 20:58:20 +01:00
LL | union U5<T> {
Show information of chain of bound obligations When the obligation that couldn't be fulfilled is specific to a nested obligation, maintain both the nested and parent obligations around for more accurate and detailed error reporting.
2020-02-18 17:53:25 -08:00
| -----------
| |
| method `clone` not found for this
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
| doesn't satisfy `U5<CloneNoCopy>: Clone`
Add more context to E0599 errors Point at the intermediary unfullfilled trait bounds.
2020-02-17 23:22:19 -08:00
...
LL | struct CloneNoCopy;
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
| ------------------- doesn't satisfy `CloneNoCopy: Copy`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
...
Update tests
2019-03-09 15:03:44 +03:00
LL | let w = u.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 17:20:14 -04:00
| ^^^^^ method cannot be called on `U5<CloneNoCopy>` due to unsatisfied trait bounds
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02: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 17:20:14 -04: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 10:40:56 +03:00
`CloneNoCopy: Copy`
which is required by `U5<CloneNoCopy>: Clone`
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
error: aborting due to 2 previous errors
hide `--explain` hint if error has no extended info
2019-04-17 13:26:38 -04:00
Some errors have detailed explanations: E0277, E0599.
Moved compile-fail tests to ui tests.
2018-08-08 14:28:26 +02:00
For more information about an error, try `rustc --explain E0277`.
Reference in New Issue Copy Permalink