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

Remove xray and improve some error messages #10427

Merged
merged 2 commits into from
Nov 12, 2013
Merged

Conversation

alexcrichton
Copy link
Member

Just a few triage issues that I ran into.

Since the removal of privacy from resolve, this flag is no longer necessary to
get the test runner working. All of the privacy checks are bypassed by a special
item attribute in the privacy visitor.

Closes rust-lang#4947
@brson
Copy link
Contributor

brson commented Nov 11, 2013

The word 'block' here isn't clear to me. Would 'closure' or even 'closure block' be a more descriptive word for where the error is occurring?

@alexcrichton
Copy link
Member Author

Updated to closure instead

@sanxiyn
Copy link
Member

sanxiyn commented Nov 12, 2013

Failed test is checking for the old error message. (return in block function instead of return in a closure.)

Before it was always stated that it was a "break outside of a loop" when you
could very well be in a loop, but just in a block instead.

Closes rust-lang#3064
bors added a commit that referenced this pull request Nov 12, 2013
Just a few triage issues that I ran into.
@bors bors closed this Nov 12, 2013
@bors bors merged commit 5fdbcc4 into rust-lang:master Nov 12, 2013
@alexcrichton alexcrichton deleted the no-xray branch November 13, 2013 22:20
flip1995 pushed a commit to flip1995/rust that referenced this pull request Mar 10, 2023
Update version attribute for 1.68 lints

Roses are red,
violets are blue,
I'm running out of rhymes,
changelogs are crimes????

---

changelog: none
<!-- changelog_checked -->
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.

4 participants