bjoernager/rust
bjoernager/rust
1
Fork 0
Code Activity

Rollup merge of #67934 - GuillaumeGomez:clean-up-e0178, r=Dylan-DPC

Browse source 
Clean up E0178 explanation

r? @Dylan-DPC
This commit is contained in:
Yuki Okushi 2020-01-07 13:46:12 +09:00 • committed by GitHub
commit 1e7a6a8b5c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 18 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

25
src/librustc_error_codes/error_codes/E0178.md
View file

@ -1,16 +1,27 @@
In types, the `+` type operator has low precedence, so it is often necessary The `+` type operator was used in an ambiguous context.
to use parentheses.
For example: Erroneous code example:
```compile_fail,E0178 ```compile_fail,E0178
trait Foo {} trait Foo {}
struct Bar<'a> { struct Bar<'a> {
w: &'a Foo + Copy, // error, use &'a (Foo + Copy) x: &'a Foo + 'a, // error!
x: &'a Foo + 'a, // error, use &'a (Foo + 'a) y: &'a mut Foo + 'a, // error!
y: &'a mut Foo + 'a, // error, use &'a mut (Foo + 'a) z: fn() -> Foo + 'a, // error!
z: fn() -> Foo + 'a, // error, use fn() -> (Foo + 'a) }
```
In types, the `+` type operator has low precedence, so it is often necessary
to use parentheses:
```
trait Foo {}
struct Bar<'a> {
x: &'a (Foo + 'a), // ok!
y: &'a mut (Foo + 'a), // ok!
z: fn() -> (Foo + 'a), // ok!
} }
``` ```