Skip to content

Conversation

@pnkfelix
Copy link
Contributor

r? anyone

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a particular reason this is an error-pattern rather than a //~ ERROR line error?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the error message was too long to go on the same line without going over 100 characters. I looked quickly at the other tests in that directory and many of them seemed to use error-pattern, e.g. bad-expr-path.rs

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW, you can put it on a later line with //~^ ERROR (the number of ^s corresponds to the number of lines above that the error should occur).

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah, good to know, I'll try to do that in the future. not really worth blocking this PR though IMO.

bors added a commit that referenced this pull request Sep 26, 2013
@bors bors closed this Sep 26, 2013
flip1995 pushed a commit to flip1995/rust that referenced this pull request Oct 6, 2022
…, r=Manishearth

Don't lint unstable moves in `std_instead_of_core`

Fixes rust-lang#9515

changelog: [`std_instead_of_core`]: No longer suggests unstable modules such as `core::error`
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