-
Notifications
You must be signed in to change notification settings - Fork 583
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
Supporting scala-async #277
Comments
Hi @balthild, Thanks for revisiting, and interesting timing. Someone else happened to ask about this inside of Twitter within the past week. We are (thankfully) no longer on scala 2.9.2, and are using scala 2.12 inside of Twitter. Right now though for our open source libraries, we're supporting 2.11, 2.12, and trying to get to 2.13 (Finatra's currently blocked there but being worked on). My expectation is that many of us on the team do feel like it's a better paradigm to program against, and that if we were starting from scratch it would be something we would certainly invest in. Given how far we've come though, I think my main concerns regarding async/await as are follows:
@vkostyukov, @mosesn, @roanta, @yufangong, @bryce-anderson - do any of you have thoughts here? |
I took a stab at integrating Twitter futures with the new async/await support in 2.13.3 (and soon 2.12.12) in the PR #279 |
As mentioned in #93,
Future
do not supprt scala-async (which introduces the wonderful async/await pattern) because c.t.utils is bound to scala 2.9.2.Now it's been a while since the library moved to scala 2.12, and I think it's time to reconsider the feature.
Related:
The text was updated successfully, but these errors were encountered: