nordic-dev.net/rust
nordic-dev.net/rust
2
0
Fork 0
mirror of https://github.com/rust-lang/rust.git synced 2024-12-10 23:54:58 +00:00
Code Issues Packages Projects Releases Wiki Activity
91351ef486
rust/tests/ui/suggestions/match-ergonomics.stderr

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

69 lines
1.8 KiB
Plaintext
Raw Normal View History

add tests
2019-04-30 02:16:35 +00:00
error[E0308]: mismatched types
--> $DIR/match-ergonomics.rs:4:10
|
check_pat_ref: use pattern_cause
2020-02-25 04:53:21 +00:00
LL | match &x[..] {
| ------ this expression has type `&[i32]`
add tests
2019-04-30 02:16:35 +00:00
LL | [&v] => {},
Modify primary span label for E0308 The previous output was unintuitive to users.
2023-01-03 02:00:33 +00:00
| ^^ expected `i32`, found `&_`
add tests
2019-04-30 02:16:35 +00:00
|
Specific labels when referring to "expected" and "found" types
2019-11-13 22:16:56 +00:00
= note: expected type `i32`
found reference `&_`
Fix suggestions for `&a: T` parameters Previously we were suggesting stuff like `fn f( &u32) {}`
2022-06-10 19:18:42 +00:00
help: consider removing `&` from the pattern
|
LL - [&v] => {},
LL + [v] => {},
bless clippy tests
2022-06-15 11:15:54 +00:00
|
add tests
2019-04-30 02:16:35 +00: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 07:40:56 +00:00
error[E0529]: expected an array or slice, found `Vec<i32>`
add tests
2019-04-30 02:16:35 +00:00
--> $DIR/match-ergonomics.rs:8:9
|
Provide a suggestion when trying to destructure a `Vec` as a slice
2021-07-10 17:54:48 +00:00
LL | match x {
| - help: consider slicing here: `x[..]`
add tests
2019-04-30 02:16:35 +00:00
LL | [&v] => {},
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 07:40:56 +00:00
| ^^^^ pattern cannot match with input type `Vec<i32>`
add tests
2019-04-30 02:16:35 +00: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 07:40:56 +00:00
error[E0529]: expected an array or slice, found `Vec<i32>`
add tests
2019-04-30 02:16:35 +00:00
--> $DIR/match-ergonomics.rs:20:9
|
Provide a suggestion when trying to destructure a `Vec` as a slice
2021-07-10 17:54:48 +00:00
LL | match x {
| - help: consider slicing here: `x[..]`
add tests
2019-04-30 02:16:35 +00:00
LL | [v] => {},
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 07:40:56 +00:00
| ^^^ pattern cannot match with input type `Vec<i32>`
add tests
2019-04-30 02:16:35 +00:00
error[E0308]: mismatched types
--> $DIR/match-ergonomics.rs:29:9
|
check_pat_ref: use pattern_cause
2020-02-25 04:53:21 +00:00
LL | match y {
| - this expression has type `i32`
add tests
2019-04-30 02:16:35 +00:00
LL | &v => {},
Modify primary span label for E0308 The previous output was unintuitive to users.
2023-01-03 02:00:33 +00:00
| ^^ expected `i32`, found `&_`
add tests
2019-04-30 02:16:35 +00:00
|
Specific labels when referring to "expected" and "found" types
2019-11-13 22:16:56 +00:00
= note: expected type `i32`
found reference `&_`
Fix suggestions for `&a: T` parameters Previously we were suggesting stuff like `fn f( &u32) {}`
2022-06-10 19:18:42 +00:00
help: consider removing `&` from the pattern
|
LL - &v => {},
LL + v => {},
bless clippy tests
2022-06-15 11:15:54 +00:00
|
add tests
2019-04-30 02:16:35 +00:00
Add if let test
2019-04-30 03:58:29 +00:00
error[E0308]: mismatched types
--> $DIR/match-ergonomics.rs:40:13
|
LL | if let [&v] = &x[..] {}
check_pat_ref: use pattern_cause
2020-02-25 04:53:21 +00:00
| ^^ ------ this expression has type `&[i32]`
Add if let test
2019-04-30 03:58:29 +00:00
| |
Modify primary span label for E0308 The previous output was unintuitive to users.
2023-01-03 02:00:33 +00:00
| expected `i32`, found `&_`
Add if let test
2019-04-30 03:58:29 +00:00
|
Specific labels when referring to "expected" and "found" types
2019-11-13 22:16:56 +00:00
= note: expected type `i32`
found reference `&_`
Fix suggestions for `&a: T` parameters Previously we were suggesting stuff like `fn f( &u32) {}`
2022-06-10 19:18:42 +00:00
help: consider removing `&` from the pattern
|
LL - if let [&v] = &x[..] {}
LL + if let [v] = &x[..] {}
bless clippy tests
2022-06-15 11:15:54 +00:00
|
Add if let test
2019-04-30 03:58:29 +00:00
error: aborting due to 5 previous errors
add tests
2019-04-30 02:16:35 +00:00
Some errors have detailed explanations: E0308, E0529.
For more information about an error, try `rustc --explain E0308`.
Reference in New Issue Copy Permalink