"Reference to class property 'enabled' is not concurrency-safe because it involves shared mutable state" with Strict Concurrency Checking = Complete about showtime

[KaneCheshire]

Hey! Thank you for raising this and for putting together a sample project. I'll take a look and try and fix it :)

[KaneCheshire]

Hey :) sorry for the delay. So I think the solution to this is to just annotate the ShowTime type with @MainActor to enforce that it and any of its properties etc can only be used in a @MainActor isolated environment.

This would mean that any place it's being used needs to be annotated with @MainActor as well; luckily UIApplicationDelegate already is annotated with @MainActor but if you're using any ShowTime property in a SwiftUI view you'll probably need to annotate the view with @MainActor explicitly, which is a bit annoying but is technically correct for async code.

[cderito]

Hi @KaneCheshire, thanks for looking into it! By annotating the ShowTime type with @MainActor what do you mean exactly? Because in my code I'm directly using its static variables so I can't do something like

@MainActor let showTime = ShowTime()

or similar, and both the App and UIApplicationDelegate in which I use it are already annotated with @MainActor.

Do you mean I should create an extension for ShowTime and annotate it?

Thank you!

[KaneCheshire]

@cderito oh sorry no I explained that badly. What I mean is, the ShowTime type itself needs to be updated in this repo to be annotated with @MainActor for strict concurrency. So it's nothing you're doing wrong at all, the compiler is just expecting us to isolate the getters and setters of the properties for strict concurrency.

My main concern with doing this is that even people who don't have strict concurrency mode enabled yet will be forced to add @MainActor to their SwiftUI views or anywhere they're accessing ShowTime properties in places not yet isolated to @MainActor 🤔

[cderito]

Oh I see! I had a 1:1 with an Apple engineer about Swift Concurrency some time after opening this issue and I got to know that there's a @preconcurrency attribute that can be used inline with import declarations to silence warnings but I couldn't get it to silence this particular warning, it seems it's dedicated to Sendable related warnings.

Anyway this will probably become an error only once Swift 6 is out so I think the fix doesn't need to be immediate, it could just be planned in a roadmap to Swift 6, or rolled out at least once this flag becomes on by default in some Xcode release, what do you think about it?

[mkoorn]

@KaneCheshire Any plans on updating the lib with a fix for this?
Thanks for your effort on this lib.