Folks, This conversation will go more smoothly if you reply as a reply, rather than in the comments. See Quinn’s Top Ten DevForums Tips for this and other tips. eoonline wrote: for the sake of future readers, that alone is insufficient. Agreed. As that’s a critical point of my previous post, I’ve edited that post to clarify it. Thanks for pointing this out. Praveenraj4256 wrote: Using Task.detached is better approach? No. In general, you should try to avoid creating new tasks wherever possible. [quote='817895022, Praveenraj4256, /thread/770655?answerId=817895022#817895022, /profile/Praveenraj4256'] I want to achieve the same functionality using structured concurrency [/quote] I think it’s a mistake to look for ‘drop in’ replacements for old techniques. The key thing to remember about Swift concurrency is that the isolation context of your code is determined statically [1]. That’s a benefit for you — you can look at the code and understand its isolation context — but it’s of critical importance to the
Topic:
Programming Languages
SubTopic:
Swift
Tags: