mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
95daa068f1
rust/src/test/ui/methods/method-call-err-msg.stderr

68 lines
2.2 KiB
Plaintext
Raw Normal View History

On mismatched argument count point at arguments
2020-02-05 23:08:07 -06:00
error[E0061]: this function takes 0 arguments but 1 argument was supplied
--> $DIR/method-call-err-msg.rs:13:7
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | fn zero(self) -> Foo { self }
Point at whole method call instead of args To avoid confusion in cases where the code is ```rust fn foo() {} / foo( | bar() | ^^^ current diagnostics point here for arg count mismatch | ); |_^ new diagnostic span points here ``` as this leads to confusion making people think that the diagnostic is talking about `bar`'s arg count, not `foo`'s. Point at `fn`s definition on arg mismatch, just like we do for closures.
2017-12-10 13:12:17 -06:00
| -------------------- defined here
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
...
Update tests
2019-03-09 06:03:44 -06:00
LL | x.zero(0)
On mismatched argument count point at arguments
2020-02-05 23:08:07 -06:00
| ^^^^ - supplied 1 argument
| |
| expected 0 arguments
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
On mismatched argument count point at arguments
2020-02-05 23:08:07 -06:00
error[E0061]: this function takes 1 argument but 0 arguments were supplied
--> $DIR/method-call-err-msg.rs:14:7
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | fn one(self, _: isize) -> Foo { self }
Point at whole method call instead of args To avoid confusion in cases where the code is ```rust fn foo() {} / foo( | bar() | ^^^ current diagnostics point here for arg count mismatch | ); |_^ new diagnostic span points here ``` as this leads to confusion making people think that the diagnostic is talking about `bar`'s arg count, not `foo`'s. Point at `fn`s definition on arg mismatch, just like we do for closures.
2017-12-10 13:12:17 -06:00
| ----------------------------- defined here
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
...
Update tests
2019-03-09 06:03:44 -06:00
LL | .one()
On mismatched argument count point at arguments
2020-02-05 23:08:07 -06:00
| ^^^- supplied 0 arguments
| |
| expected 1 argument
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
On mismatched argument count point at arguments
2020-02-05 23:08:07 -06:00
error[E0061]: this function takes 2 arguments but 1 argument was supplied
--> $DIR/method-call-err-msg.rs:15:7
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | fn two(self, _: isize, _: isize) -> Foo { self }
Point at whole method call instead of args To avoid confusion in cases where the code is ```rust fn foo() {} / foo( | bar() | ^^^ current diagnostics point here for arg count mismatch | ); |_^ new diagnostic span points here ``` as this leads to confusion making people think that the diagnostic is talking about `bar`'s arg count, not `foo`'s. Point at `fn`s definition on arg mismatch, just like we do for closures.
2017-12-10 13:12:17 -06:00
| --------------------------------------- defined here
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
...
Update tests
2019-03-09 06:03:44 -06:00
LL | .two(0);
On mismatched argument count point at arguments
2020-02-05 23:08:07 -06:00
| ^^^ - supplied 1 argument
| |
| expected 2 arguments
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
Unify output of "variant not found" errors
2020-01-08 10:05:31 -06:00
error[E0599]: no method named `take` found for struct `Foo` in the current scope
On mismatched argument count point at arguments
2020-02-05 23:08:07 -06:00
--> $DIR/method-call-err-msg.rs:19:7
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | pub struct Foo;
Add more context to E0599 errors Point at the intermediary unfullfilled trait bounds.
2020-02-18 01:22:19 -06:00
| ---------------
| |
| method `take` 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 02:40:56 -05:00
| doesn't satisfy `Foo: Iterator`
Point to ADT definition when not finding variant, method, assoc type
2017-11-16 00:18:52 -06:00
...
Update tests
2019-03-09 06:03:44 -06:00
LL | .take()
Give method not found a primary span label
2019-09-06 14:00:07 -05:00
| ^^^^ method not found in `Foo`
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
|
Track all predicates in errors, not just trait obligations Surface associated type projection bounds that could not be fulfilled in E0599 errors. Always present the list of unfulfilled trait bounds, regardless of whether we're pointing at the ADT or trait that didn't satisfy it.
2020-02-18 18:35:47 -06:00
= note: the method `take` exists but 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
`Foo: Iterator`
which is required by `&mut Foo: Iterator`
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
= help: items from traits can only be used if the trait is implemented and in scope
Do not suggest implementing traits if present in predicates
2020-02-25 14:10:48 -06:00
= note: the following trait defines an item `take`, 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: `Iterator`
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
On mismatched argument count point at arguments
2020-02-05 23:08:07 -06:00
error[E0061]: this function takes 3 arguments but 0 arguments were supplied
--> $DIR/method-call-err-msg.rs:21:7
|
LL | fn three<T>(self, _: T, _: T, _: T) -> Foo { self }
| ------------------------------------------ defined here
...
LL | y.three::<usize>();
| ^^^^^--------- supplied 0 arguments
| |
| expected 3 arguments
error: aborting due to 5 previous errors
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
hide `--explain` hint if error has no extended info
2019-04-17 12:26:38 -05:00
Some errors have detailed explanations: E0061, E0599.
update tests
2018-03-03 08:59:40 -06:00
For more information about an error, try `rustc --explain E0061`.
Reference in New Issue Copy Permalink