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

Warnings beyond the first to the same position are dropped #6120

Closed
scabug opened this issue Jul 21, 2012 · 4 comments
Closed

Warnings beyond the first to the same position are dropped #6120

scabug opened this issue Jul 21, 2012 · 4 comments
Assignees
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Jul 21, 2012

All warnings beyond the first to the same position are silently dropped. Since they may be about unrelated matters, this is less than ideal. Martin says:

What we could do:

1) there may only be one error reported in any position
2) If an error is reported in a position no warning can be reported in
the same position
3) if there is no error reported in some position, any number of
warnings may be reported in that position.

This would certainly solve the problem for me - my concern is with the set of warnings issued on successful compilation runs (which are likely to be inferred by the user to be the complete set of normal warnings.)

@scabug
Copy link
Author

@scabug scabug commented Jul 21, 2012

@scabug
Copy link
Author

@scabug scabug commented Jul 21, 2012

@paulp said:
Oh geez, I found this comment written 2 years, 5 months ago, by me of course.

/** Note: if a symbol has both @deprecated and @migration annotations and both
 *  warnings are enabled, only the first one checked here will be emitted.
 *  I assume that's a consequence of some code trying to avoid noise by suppressing
 *  warnings after the first, but I think it'd be better if we didn't have to
 *  arbitrarily choose one as more important than the other.
 */

@scabug
Copy link
Author

@scabug scabug commented May 20, 2013

@JamesIry said:
2.10.2 is about to be cut. Kicking down the road and un-assigning to foster work stealing.

@scabug scabug closed this Sep 27, 2013
@scabug
Copy link
Author

@scabug scabug commented Sep 27, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants