Skip to content

Do not accidentally force diagnostic message in reportWarning #2348

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

Merged
merged 2 commits into from
May 2, 2017

Conversation

felixmulder
Copy link
Contributor

No description provided.

@felixmulder felixmulder requested a review from smarter May 2, 2017 13:27
@felixmulder felixmulder force-pushed the topic/cleanup-spree branch from cb436b3 to 49c8744 Compare May 2, 2017 14:06
Diagnostic messages are contained within a `MessageContainer` which
takes the message by name. This is in order for the compiler to be able
to throw away messages without evaluting potentially costly operations.
Calling `.contained` breaks this laziness.
@felixmulder felixmulder force-pushed the topic/cleanup-spree branch from 49c8744 to ee1160c Compare May 2, 2017 14:07
Copy link
Member

@smarter smarter left a comment

Choose a reason for hiding this comment

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

Maybe we should rename contained to something that make it clear thtat it forces things, I don't know.

@smarter
Copy link
Member

smarter commented May 2, 2017

One way would be to call it contained() and not contained

@smarter smarter changed the title Make sure reportWarning doesn't break by name Do not accidentally force diagnostic message in reportWarning May 2, 2017
@felixmulder felixmulder force-pushed the topic/cleanup-spree branch from 8dcedc7 to 69bbf85 Compare May 2, 2017 14:17
@felixmulder felixmulder merged commit df22149 into scala:master May 2, 2017
@allanrenucci allanrenucci deleted the topic/cleanup-spree branch December 14, 2017 19:25
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.

2 participants