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

SIP-18 produces incorrect count of suppressed warnings #5675

Closed
scabug opened this issue Apr 16, 2012 · 4 comments
Closed

SIP-18 produces incorrect count of suppressed warnings #5675

scabug opened this issue Apr 16, 2012 · 4 comments
Assignees
Milestone

Comments

@scabug
Copy link

@scabug scabug commented Apr 16, 2012

When SIP-18 warnings are not displayed, scalac may produce an incorrect count. For example:

dcs@shadowfax:~/tmp/ForwardPipe$ scalac PostFix.scala 
warning: there were 2 feature warnings; re-run with -feature for details
one warning found
dcs@shadowfax:~/tmp/ForwardPipe$ scalac -feature PostFix.scala 
PostFix.scala:4: warning: postfix operator != should be enabled
by making the implicit value language.postfixOps visible.
This can be achieved by adding the import clause 'import language.postfixOps'
or by setting the compiler option -language:postfixOps.
See the Scala docs for value scala.language.postfixOps for a discussion
why the feature should be explicitly enabled.
    val a = list filter (2 !=)
                           ^
one warning found

(file attached)

@scabug
Copy link
Author

@scabug scabug commented Apr 16, 2012

Imported From: https://issues.scala-lang.org/browse/SI-5675?orig=1
Reporter: @dcsobral
Attachments:

  • PostFix.scala (created on Apr 16, 2012 6:15:44 PM UTC, 147 bytes)

@scabug
Copy link
Author

@scabug scabug commented Jun 11, 2012

@adriaanm said:
Hubert, could you please have a look or re-assign?

@scabug
Copy link
Author

@scabug scabug commented Feb 4, 2013

@scabug
Copy link
Author

@scabug scabug commented Feb 8, 2013

@JamesIry said:
superseded by scala/scala#2095

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