You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a ViewController that conforms to the JTACMonthViewDelegate protocol. With strict concurrency warnings turned on, the compiler complains that "Main-actor isolated instance method cannot be used to satisfy nonisolated protocol requirement` since the ViewController is obviously marked @mainactor. I think all the view dependent delegate protocols (and probably also the data source protocols) should be marked @mainactor, since they are probably called from the main actor anyways. This is also how UICollectionViewDelegate and DataSources are marked.
Steps To Reproduce
Conform a ViewController to a delegate like JTACMonthViewDelegate with swift strict concurrency warnings set to complete.
Expected Behavior
The compiler shouldn't complain about nonisolated protocol requirements.
The text was updated successfully, but these errors were encountered:
hmmm...
if i put mainactorinto this library, i think this will raise the minimum OS requirement?
if yes, then is there another way around this? I am unfamiliar with mainactor
(Required) Version Number: 8.0.5
Description
I've got a ViewController that conforms to the
JTACMonthViewDelegate
protocol. With strict concurrency warnings turned on, the compiler complains that "Main-actor isolated instance method cannot be used to satisfy nonisolated protocol requirement` since the ViewController is obviously marked @mainactor. I think all the view dependent delegate protocols (and probably also the data source protocols) should be marked @mainactor, since they are probably called from the main actor anyways. This is also how UICollectionViewDelegate and DataSources are marked.Steps To Reproduce
Conform a ViewController to a delegate like
JTACMonthViewDelegate
with swift strict concurrency warnings set tocomplete
.Expected Behavior
The compiler shouldn't complain about nonisolated protocol requirements.
The text was updated successfully, but these errors were encountered: