Skip to content

Conversation

@geoffhill-zz
Copy link

Since lint check attributes are the preferred way of selectively
enabling/disabling lint checks, the output format of a failed
default check has been changed to reflect that.

When lint checks are being explicitly set by a command-line flag
or an attribute, the behavior is unchanged, so that the user can
quickly pinpoint the source.

Since lint check attributes are the preferred way of selectively
enabling/disabling lint checks, the output format of a failed
default check has been changed to reflect that.

When lint checks are being explicitly set by a command-line flag
or an attribute, the behavior is unchanged, so that the user can
quickly pinpoint the source.
@geoffhill-zz
Copy link
Author

#6580

@alexcrichton
Copy link
Member

Looks good to me, thanks!

Could you also add a test to make sure that functionality like this doesn't regress? It would involve adding a test file to src/test/compile-fail with a directive of the form //~ ERROR: my text here.

There should be lots of examples in adjacent files (although ignore the ones with error-pattern, it's not as precise of an error check), and if you need any help feel free to ping me on IRC (acrichto) or comment here.

Also, could you put the words Closes #6580 in the commit message as well? That'll appease github to auto-close the issue as soon as this is merged into master.

@alexcrichton
Copy link
Member

Closing in favor of #9782

bors added a commit that referenced this pull request Oct 9, 2013
Since lint check attributes are the preferred way of selectively
enabling/disabling lint checks, the output format of a failed
default check has been changed to reflect that.

When lint checks are being explicitly set by a command-line flag
or an attribute, the behavior is unchanged, so that the user can
quickly pinpoint the source.

Supersedes the patch suggested in #9778
Closes #6580
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.

3 participants