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

48 lines
1.6 KiB
Plaintext
Raw Normal View History

Pass the full span for method calls
2017-10-08 20:13:37 -05:00
error[E0061]: this function takes 0 parameters but 1 parameter was supplied
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/method-call-err-msg.rs:12: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)
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
| ^^^^ expected 0 parameters
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
error[E0061]: this function takes 1 parameter but 0 parameters were supplied
Remove licenses
2018-12-25 09:56:47 -06:00
--> $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 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()
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
| ^^^ expected 1 parameter
error[E0061]: this function takes 2 parameters but 1 parameter was supplied
Remove licenses
2018-12-25 09:56:47 -06:00
--> $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 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);
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
| ^^^ expected 2 parameters
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
error[E0599]: no method named `take` found for type `Foo` in the current scope
Remove licenses
2018-12-25 09:56:47 -06:00
--> $DIR/method-call-err-msg.rs:18: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;
Point to ADT definition when not finding variant, method, assoc type
2017-11-16 00:18:52 -06:00
| --------------- method `take` not found for this
...
Update tests
2019-03-09 06:03:44 -06:00
LL | .take()
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
| ^^^^
|
= note: the method `take` exists but the following trait bounds were not satisfied:
`&mut Foo : std::iter::Iterator`
= help: items from traits can only be used if the trait is implemented and in scope
= note: the following traits define an item `take`, perhaps you need to implement one of them:
Do not suggest private traits that have missing method When encountering a method call for an ADT that doesn't have any implementation of it, we search for traits that could be implemented that do have that method. Filter out private non-local traits that would not be able to be implemented. This doesn't account for public traits that are in a private scope, but works as a first approximation and is a more correct behavior than the current one.
2018-01-17 22:15:13 -06:00
candidate #1: `std::io::Read`
candidate #2: `std::iter::Iterator`
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
error: aborting due to 4 previous errors
update tests
2018-03-03 08:59:40 -06:00
Some errors occurred: E0061, E0599.
For more information about an error, try `rustc --explain E0061`.
Reference in New Issue Copy Permalink