Yes! I'll send the Matt Signal. Thank you so much 🙏

I did that, but without understanding what swift6 tries to solve, it was just very difficult. I mindlessly added Sendable and MainActor here and there just to silent the compiler. And it backfires.

But yeah, if I didn't start with something, I wouldn't know what to search for.

Luckily, there are a ton of articles on this. I read both yours and Donny's.

I'm to blame for this. I didn't catch up when Swift 6 was introduced. I was waiting for the approachable concurrency to release to catch up at once. That's why.

This feels like Swift 3 all over again.

Not disappointed, just overwhelmed.

I thought I can just figure things out 1 error at a time, but no. Without knowing the whole thing, there's no way I could understand what's going on. I can't even understand the error message.

I need to read and compare the before and after of Swift 6 & 6.2.

Much better than yesterday. That's for sure. 😬

Got it. 🙏

What check are you referring to, by the way?

I can always stay in swift 5, but I just think it's a good idea to learn the new stuff.

Anyway, thank you so much for your help. Really appreciate your time. 🙏

Maybe I'm an idiot, but what if I keep using Swift 5?

Yes, Swift 6 is supposed to help make concurrency safer, but it definitely comes with its own challenge. And also, my apps are generally small apps anyway.

making the extension nonisolated fixes it. Gosh! I could never guess this is an issue.

And sadly, this is what I refer to in my original post. I didn't have this concurrency issue before but now I do.

this is where my lack of knowledge on concurrency is causing me trouble.

1. How do you know it will run on background thread?

2. I'm going to read up on when to use the @.Sendable closure. This is a blur right now.

3. Things like this, I really expect the compiler to help spot the issue.

you mean... something like this?

I don't know if this is the root cause or not, but I see this file as part of the trace. What do you think?

I just want a convenient method where I can initialize a Color that adapts to both light and dark.

I see... Got it.

Hmm... I'm struggling to read the backtrace. If it's something to do with my code, it normally points me to where it originates from. But I can't seem to find any.

And what you say about missing @.Sendable, it sounds to me like something a compiler could catch. No?

Matt Signal

2. Honestly, I'm not sure what's wrong. The error is related to AsyncRenderer, which is related to UI. However, I didn't do anything apart from trying to fix all the errors after switching to Swift 6.2. Xcodes doesn't point to where causing the error, so I'm trying to comment out code to find out.

1. Both Approachable Concurrency and default MainActor. It's 2 separate settings, but I'm under the impression that setting both is the norm now. Right?

I refer to the Swift 6.2 (approachable concurrency). Honestly, the main issue is me. My knowledge on concurrency is limited. And someway somehow, after I fix all the errors and the code compiles again, I get error with thread that doesn't happen on Swift 5.