Post #1839171
2026-04-07 17:07 UTC
@mattiem @matthew @akbashev OK, I'm glad you've posted this, because my thinking is on the right track!
Definitely going to need some time for re-learning things, but that was going to be necessary as Approachable Concurrency inevitably becomes default anyway.
My idea is that bigger code bases with more tests will benefit even more from this approach, because you have fewer constraints on where you can use types, less MainActor contention in tests, and it'll be easier to tell…
Replies (1)
-
@rhysmorgan@mastodon.social 2026-04-07 17:09
@mattiem @matthew @akbashev …for everyone, where a method is running, async or not. Approachable Concurrency making async methods behave the same way Task has is a good start, and hopefully the @.concurrent keyword will reduce the proliferation of inappropriate Task.detached usage you see throughout codebases, often with a git blame that dates back a few years 😃