RetroFed Forum
Your home away from modern life.
Search Categories Forum list Register Log in
About RetroFed
RetroFed

Welcome to the nostalgia-filled piefed instance of yesteryear.

Open Registration with Application questionnaire.

If you have a question or comment you can post in !meta@retrofed.com or message @DosDude@retrofed.com or @Die4Ever@retrofed.com

In case of downtime and/or emergency, we will post updates on @DosDude@mastodon.social

Some rules we try to uphold:

  • Be civil. Bigotry is not welcome. This includes (but is not limited to): transphobia, queerphobia, racism, ageism and ableism. We do not promote hate.
  • Communities need to be Retro or Retro-adjacent.
  • Please don't upload pornographic content. (use an external image host for that)
72 registered users
Administrators: DosDude, Die4Ever
Visit retrofed.com
isolated(any) and #isolation - Letting Swift Closures Automatically Inherit Isolation
Post Reply RetroFed Forum Forum Index » Swift
AuthorMessage
Yang programming.dev fatbobman@programming.dev
Joined: 2024-04-11
Quote

Link: https://fatbobman.com/en/posts/letting-swift-closures-automatically-inherit-isolation/

Why does the compiler still demand @MainActor in even when Default Actor Isolation is enabled? 🤔
Discover how to use @isolated(any) and #isolation to let your functions automatically inherit their caller's context in Swift 6.
1   Original
Post Reply
Back to top
Powered by PieFed · PieBB frontend · All times are Europe/Amsterdam