10000 upgrade to sbt 0.13.15 by SethTisue · Pull Request #5775 · scala/scala · GitHub
[go: up one dir, main page]

Skip to content

upgrade to sbt 0.13.15 #5775

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 1 commit into from
Apr 18, 2017
Merged

upgrade to sbt 0.13.15 #5775

merged 1 commit into from
Apr 18, 2017

Conversation

SethTisue
Copy link
Member
@SethTisue SethTisue commented Mar 14, 2017

WIP, not to be merged until 0.13.14 final is released.
for now, just making sure it passes CI.

fyi @eed3si9n @dwijnand

@scala-jenkins scala-jenkins added this to the 2.12.2 milestone Mar 14, 2017
@SethTisue SethTisue added the WIP label Mar 14, 2017
@SethTisue SethTisue modified the milestones: WIP, 2.12.2 Mar 14, 2017
@dwijnand
Copy link
Member

Thanks Seth. Yay! It passed.

@SethTisue SethTisue changed the title upgrade to sbt 0.13.14-RC1 upgrade to sbt 0.13.14 Mar 21, 2017
@SethTisue
Copy link
Member Author

rebased, bumped to 0.13.14-RC2

we do not speak of sbt 0.13.14. move along, move along.
@SethTisue SethTisue changed the title upgrade to sbt 0.13.14 upgrade to sbt 0.13.15 Apr 10, 2017
@SethTisue
Copy link
Member Author

rebased, bumped to 0.13.15. I suggest we wait until 2.12.2 is out before merging, on the off chance it could somehow mess up the release.

@SethTisue SethTisue removed the WIP label Apr 10, 2017
@SethTisue SethTisue modified the milestones: 2.12.3, WIP Apr 10, 2017
@SethTisue SethTisue self-assigned this Apr 10, 2017
@SethTisue SethTisue merged commit 4efab51 into scala:2.12.x Apr 18, 2017
@SethTisue SethTisue deleted the sbt-0.14 branch April 18, 2017 18:41
eed3si9n pushed a commit to eed3si9n/scala that referenced this pull request May 14, 2019
To avoid deadlocks when combining objects, lambdas and multi-threading,
lambdas in objects are compiled to instance methods of the module class
instead of static methods (see tests/run/deadlock.scala and
scala/scala-dev#195 for details).

This has worked well for us so far but this is problematic for
serialization: serializing a lambda requires serializing all the values
it captures, if this lambda is in an object, this means serializing the
enclosing object, which fails if the object does not extend
Serializable.

Because serializing objects is basically free since scala#5775, it seems like
the simplest solution is to simply make all objects Serializable, this
certainly seems preferable to deadlocks.

This commit causes a cyclic reference to happen in some cases, we add a
workaround to avoid this in Trees.scala and fix it properly in the
commit.
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.

3 participants
0