Swift 6 makes writing code miserable
Keep in mind that the Swift 6 language mode is optional; you can always revert to Swift 5 mode.
In general, I’m the opposite an early adopter. I let other folks deal with all the grief associated with new OS versions, APIs, and tools. By the time I get around to it, the early adopters have encounter all the bumps, and either smoothed them over or published a map for how to avoid them.
Now, Swift concurrency is an exception to my general rule because I’m super interested in this technology. But that’s just me. It’s fine for you to take your time here. Adoption is only going to get easier as the tools, SDKs, and documentation improve.
it looks like it's a misleading compiler error
Right. That’s why I was trying to reproduce it. I originally suspected that this was caused by you putting both values into a tuple, but I wasn’t able to confirm that because I could never reproduce the problem. If you can help me out there, that’d be grand.
Oh, and it’ll also make for a reduced test project that you can use to file a bug about the misleading diagnostics.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"