Skip to content

clean up E0185 explanation #68070

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bors merged 3 commits into from
Jan 11, 2020
Merged

clean up E0185 explanation #68070

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f79ba85
clean up E0185 explanation
GuillaumeGomez Jan 9, 2020
c899f67
Improve E0185 wording
GuillaumeGomez Jan 10, 2020
4fadb50
Update E0185.md
Dylan-DPC Jan 10, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update E0185.md
  • Loading branch information
@Dylan-DPC
Dylan-DPC authored Jan 10, 2020
commit 4fadb507f48a0f959518bbf9b7d0969a159d76f1
4 changes: 2 additions & 2 deletions src/librustc_error_codes/error_codes/E0185.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,8 +19,8 @@ impl Foo for Bar {
```

When a type implements a trait's associated function, it has to use the same
signature. So in this case, since `Foo::foo` doesn't take any argument and
doesn't return anything, its implementation on `Bar` should be the same:
signature. So in this case, since `Foo::foo` does not take any argument and
does not return anything, its implementation on `Bar` should be the same:

```
trait Foo {
Expand Down