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
Local in scala.concurrent #9835
Comments
Imported From: https://issues.scala-lang.org/browse/SI-9835?orig=1 |
Would you accept a PR for this? If so it might be a good first issue. |
@eed3si9n I have some concerns, but it would be interesting to see what a solution would look like. (I have some Future improvements in the works: https://github.com/viktorklang/scala-futures) |
the usual gatekeeper on this is @viktorklang. I'll provisionally add the "good first issue" label because unlike many scala/scala repo things this is pretty self-contained, no big ramp-up required. but anyone interested should be advised that they should propose a design and run it by https://contributors.scala-lang.org before writing a bunch of code |
I made a "concurrency" label, we strangely didn't have one. |
@SethTisue Thanks for creating the label, Seth! |
Does it need deep understanding of concurrency in Scala? |
I don't know about "deep", but you should probably have some experience working with |
|
@jsw you might try starting a thread on it on https://contributors.scala-lang.org to call attention to this? |
@SethTisue Thanks for the suggestion. For reference, pasting a link here https://contributors.scala-lang.org/t/locals-in-scala-concurrent/1785 |
It would be nice to have something equivalent to Twitter's Local in scala.concurrent.
In other words, something like Java's ThreadLocal which follows the application flow (rather than JVM threads) when using
scala.concurrent.Future
?The text was updated successfully, but these errors were encountered: