-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sendable conformance #40
Comments
Interesting! I haven’t used Swift Concurrency much myself yet so I’m not so familiar in this area, but I think that you are right. Is this a case of me having to add |
An Apple Frameworks Engineer specifies that https://forums.developer.apple.com/forums/thread/732362 Unfortunately I don't think that we can do anything about this from our side. I guess that you might need to load the resource into a I'm going to close this issue for now, but please reopen it if you feel that there is something that can be done here. Thanks! |
Thank you for looking into this! And apologies for not replying the last few days. That's a very interesting find! |
Me neither 😄 Maybe I should leave this open a bit longer then.. Would it be possible for you to share a code example that surfaces the issue that you are describing? I'm not quite sure how to reproduce the warning that you are seeing. |
Sure, writing it by memory, but if I'm not wrong was something like this: struct SomeView: View {
var body: some View {
myVarView
}
@MainActor
@ViewBuilder
var myVarView: some View {
Text(.localizable.footerText(items.count)) // <- warning
}
} |
Sorry for the delay, but I tried replicating this in the demo app and I can't seem to reproduce the warning that you described. If you get some time, please can you share a project that replicates the issue? Using the demo project might help if you can't share your own source code |
Thanks for open sourcing this!
Using it on some parts marked
@MainActor
. Xcode produces the following warnings:Being static strings I think we should be able to make it @sendable? 🤔
The text was updated successfully, but these errors were encountered: