Upgrade to Scala 2.12.12, 2.13.3#1199
Merged
xerial merged 1 commit intowvlet:masterfrom Aug 3, 2020
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1199 +/- ##
=======================================
Coverage 83.20% 83.20%
=======================================
Files 289 289
Lines 11042 11042
Branches 732 732
=======================================
Hits 9187 9187
Misses 1855 1855 Continue to review full report at Codecov.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These Scala versions added
-Xasyncoption, so that scala-async can be efficiently implemented by using the compile-time information. The previous version of scala-async was a macro-based implementation, which was slow and incomplete.Related:
scala-async will support Scala.js too. This would be useful for writing Future-based async code instead of writing chains of Futures (e.g., Conductor's Future-based operation code will benefit from scala-async). I think reading this SIP https://docs.scala-lang.org/sips/async.html is good enough to understand the motivation why scala-async was developed.