mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
8c75e18e5d
rust/src/test/ui/span/missing-unit-argument.stderr

71 lines
2.3 KiB
Plaintext
Raw Normal View History

Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
error[E0061]: this function takes 1 parameter but 0 parameters were supplied
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
--> $DIR/missing-unit-argument.rs:21:33
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | let _: Result<(), String> = Ok(); //~ ERROR this function takes
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
| ^^^^
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
help: expected the unit value `()`; create it with empty parentheses
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
|
Update UI tests
2018-02-24 17:01:39 -06:00
LL | let _: Result<(), String> = Ok(()); //~ ERROR this function takes
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
| ^^
error[E0061]: this function takes 2 parameters but 0 parameters were supplied
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
--> $DIR/missing-unit-argument.rs:22:5
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | fn foo(():(), ():()) {}
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
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
...
Update UI tests
2018-02-22 18:42:32 -06:00
LL | foo(); //~ ERROR this function takes
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
| ^^^^^ expected 2 parameters
error[E0061]: this function takes 2 parameters but 1 parameter was supplied
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
--> $DIR/missing-unit-argument.rs:23:5
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | fn foo(():(), ():()) {}
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
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
...
Update UI tests
2018-02-22 18:42:32 -06:00
LL | foo(()); //~ ERROR this function takes
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
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
error[E0061]: this function takes 1 parameter but 0 parameters were supplied
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
--> $DIR/missing-unit-argument.rs:24:5
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | fn bar(():()) {}
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
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
...
Update UI tests
2018-02-22 18:42:32 -06:00
LL | bar(); //~ ERROR this function takes
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
| ^^^^^
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
help: expected the unit value `()`; create it with empty parentheses
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
|
Update UI tests
2018-02-24 17:01:39 -06:00
LL | bar(()); //~ ERROR this function takes
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
| ^^
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
--> $DIR/missing-unit-argument.rs:25:7
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | fn baz(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 UI tests
2018-02-22 18:42:32 -06:00
LL | S.baz(); //~ ERROR this function takes
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
| ^^^
help: expected the unit value `()`; create it with empty parentheses
|
Update UI tests
2018-02-24 17:01:39 -06:00
LL | S.baz(()); //~ ERROR this function takes
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
--> $DIR/missing-unit-argument.rs:26:7
|
Update UI tests
2018-02-22 18:42:32 -06:00
LL | fn generic<T>(self, _: T) { }
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 UI tests
2018-02-22 18:42:32 -06:00
LL | S.generic::<()>(); //~ ERROR this function takes
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
| ^^^^^^^
help: expected the unit value `()`; create it with empty parentheses
|
Update UI tests
2018-02-24 17:01:39 -06:00
LL | S.generic::<()>(()); //~ ERROR this function takes
Pass the full span for method calls
2017-10-08 20:13:37 -05:00
| ^^
error: aborting due to 6 previous errors
Suggest `Ok(())` when encountering `Ok()`
2017-08-23 08:40:05 -05:00
Update ui tests
2018-02-19 14:40:25 -06:00
If you want more information on this error, try using "rustc --explain E0061"
Reference in New Issue Copy Permalink