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
-Xasync
option, 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.