Thank you for the reply and extended info! Part of the effort was to see how/if -disable-dynamic-actor-isolation works. After a day of testing I'd say it really works for iOS targets and not working for me for the watch target, there is a chance I'm applying the flag wrong. I updated the watch target now to count with the dynamic concurrency checks.
I wonder when/if staying on swift 5 will become "penalized" by facing obstacles when new swift and xcode versions come.
Topic:
Programming Languages
SubTopic:
Swift
Tags: