Skip to content

SI-7624 Fix -feature and some -Xlint warnings#2705

Closed
soc wants to merge 4 commits intoscala:masterfrom
soc:SI-7624
Closed

SI-7624 Fix -feature and some -Xlint warnings#2705
soc wants to merge 4 commits intoscala:masterfrom
soc:SI-7624

Conversation

@soc
Copy link
Copy Markdown
Contributor

@soc soc commented Jul 5, 2013

Changes build.xml to build Scala with -feature enabled.

soc added 2 commits July 5, 2013 15:52
I left one warning untouched, because instead of adding the import the
diagnostics should be fixed:

    scala/src/library/scala/collection/parallel/mutable/LazyCombiner.scala:33:
    warning: the existential type
        scala.collection.parallel.mutable.LazyCombiner[_$1,_$2,_$3] forSome {
          type _$1; type _$2; type _$3 <: scala.collection.generic.Growable[_$1] with scala.collection.generic.Sizing },
    which cannot be expressed by wildcards, should be enabled by making the implicit value scala.language.existentials visible.
    if (other.isInstanceOf[LazyCombiner[_, _, _]]) {
                       ^
@soc
Copy link
Copy Markdown
Contributor Author

soc commented Jul 5, 2013

I have not modified BCode-related source files, because I don't want to cause any trouble when @magarciaEPFL pushes the next round of improvements.

@soc
Copy link
Copy Markdown
Contributor Author

soc commented Jul 5, 2013

Review by @adriaanm/@phaller.

@soc soc closed this Jul 5, 2013
@soc soc reopened this Jul 5, 2013
@scala-jenkins
Copy link
Copy Markdown

IDE validation running at https://scala-webapps.epfl.ch/jenkins/job/pr-scala/94/

@scala-jenkins
Copy link
Copy Markdown

IDE validation running at https://scala-webapps.epfl.ch/jenkins/job/pr-scala/95/

@scala-jenkins
Copy link
Copy Markdown

IDE validation running at https://scala-webapps.epfl.ch/jenkins/job/pr-scala/96/

@adriaanm
Copy link
Copy Markdown
Contributor

adriaanm commented Jul 6, 2013

Nice! We should really get to a state where people can compile with -fatal-warnings (this may include a switch that suppresses inliner warnings). Also, one improvement to deprecation warnings would be not to warn when a deprecated member is called from a member that is similarly deprecated (as they will both disappear together)

@som-snytt
Copy link
Copy Markdown
Contributor

@adriaanm Deprecation is already suppressed as you describe. I don't know about "similarly". If two members are differentially deprecated, one will disappear first. In that case, -Xfuture -Xlint could emit the warning, "Don't you know that the method you're calling will be removed before you will?"

@adriaanm
Copy link
Copy Markdown
Contributor

Sorry, this can't be merged anymore, and I didn't want to merge it right before a release.
Could your rebased and resubmit next week -- thanks!

@adriaanm adriaanm closed this Jul 12, 2013
@soc
Copy link
Copy Markdown
Contributor Author

soc commented Jul 12, 2013

@adriaanm: Rebased and submitted: #2727

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