mikros/rust
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Rollup merge of #69457 - GuillaumeGomez:clean-up-e0370-e0371, r=Dylan-DPC

Browse Source 
Clean up e0370 e0371

r? @Dylan-DPC
This commit is contained in:
Dylan DPC 2020-02-26 02:07:17 +01:00 committed by GitHub
commit 35ae48c735
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 10 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
src/librustc_error_codes/error_codes/E0370.md
View File

@ -1,5 +1,7 @@
The maximum value of an enum was reached, so it cannot be automatically
set in the next enum value. Erroneous code example:
set in the next enum value.
Erroneous code example:
```compile_fail,E0370
#[repr(i64)]

12
src/librustc_error_codes/error_codes/E0371.md
View File

@ -1,9 +1,6 @@
When `Trait2` is a subtrait of `Trait1` (for example, when `Trait2` has a
definition like `trait Trait2: Trait1 { ... }`), it is not allowed to implement
`Trait1` for `Trait2`. This is because `Trait2` already implements `Trait1` by
definition, so it is not useful to do this.
A trait was implemented on another which already automatically implemented it.
Example:
Erroneous code examples:
```compile_fail,E0371
trait Foo { fn foo(&self) { } }
@ -15,3 +12,8 @@ impl Foo for Baz { } // error, `Baz` implements `Bar` which implements `Foo`
impl Baz for Baz { } // error, `Baz` (trivially) implements `Baz`
impl Baz for Bar { } // Note: This is OK
```
When `Trait2` is a subtrait of `Trait1` (for example, when `Trait2` has a
definition like `trait Trait2: Trait1 { ... }`), it is not allowed to implement
`Trait1` for `Trait2`. This is because `Trait2` already implements `Trait1` by
definition, so it is not useful to do this.