Skip to content

Fix #8058: Fix isStableMember test #8062

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 3 commits into from
Jan 22, 2020
Merged

Conversation

odersky
Copy link
Contributor

@odersky odersky commented Jan 22, 2020

isStableMember classified NoSymbol as stable. This meant that
an Application without a symbol was classified as pure in TreeInfo.
This in turn meant that the application could be dropped and replaced
with Unit at the end of a block. The (non-)pure application in
the test was an array update.

isStableMember classified NoSymbol as stable. This meant that
an Application without a symbol was classified as pure in TreeInfo.
This in turn meant that the application could be dropped and replaced
with `Unit` at the end of a block. The (non-)pure application in
the test was an array update.
Before the fix to scala#8058, a reference `x` with constant type `0` was
deemed to have a stable member symbol since its symbol did not exist.
That's what gave the reference the `PurePath` status. Now that
`isStableMember` is fixed, this needs to be asserted
explicitly.
TermRefs that do not have a symbol should not be widened under widenIfUnstable.
@odersky
Copy link
Contributor Author

odersky commented Jan 22, 2020

We get an unresolved dependency in dotty-bootstrap:

org.scala-js#scalajs-linker_2.12;1.0.0-RC2:

That's what causes all the builds to fail.

@smarter
Copy link
Member

smarter commented Jan 22, 2020

sigh, we got banned from sonatype again, I'll look into it:

<h1>Error 403 Forbidden</h1>
    <p>You’ve been blocked from this operation due to violation of the Central terms of service. Please see https://central.sonatype.org/blacklisted to remediate this issue.</p>

@smarter
Copy link
Member

smarter commented Jan 22, 2020

Should be OK if you rebase on master now that #8071 is merged.

@odersky
Copy link
Contributor Author

odersky commented Jan 22, 2020

Great, thanks for the quick intervention!

@odersky odersky requested a review from smarter January 22, 2020 20:45
@smarter smarter merged commit 5a86c1f into scala:master Jan 22, 2020
@smarter smarter deleted the fix-#8058 branch January 22, 2020 20:54
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