Skip to content
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.

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

Fix error message when trait method ends with wrong token #8547

Closed
wants to merge 1 commit into from

Conversation

lilyball
Copy link
Contributor

When parsing a trait function, the function must end with either ; or
{ (signifying a default implementation). The error message incorrectly
stated that it must be ; or }.

Fixes #6610.

When parsing a trait function, the function must end with either `;` or
`{` (signifying a default implementation). The error message incorrectly
stated that it must be `;` or `}`.

Fixes rust-lang#6610.
bors added a commit that referenced this pull request Aug 18, 2013
When parsing a trait function, the function must end with either `;` or
`{` (signifying a default implementation). The error message incorrectly
stated that it must be `;` or `}`.

Fixes #6610.
@bors bors closed this Aug 18, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Mar 24, 2022
More `transmute_undefined_repr` fixes

fixes: rust-lang#8498
fixes: rust-lang#8501
fixes: rust-lang#8503

changelog: Allow `transumte_undefined_repr` between fat pointers and `(usize, usize)`
changelog: Allow `transumte_undefined_repr` when one side is a union
changelog: Fix `transumte_undefined_repr` on tuples with one non-zero-sized type.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

error: expected ; or } but found }
3 participants