Rob NapierMar 20, 2024

I anticipate a long future of an ambiguous meaning of `@\unchecked Sendable`:

Meaning 1 (the official meaning):
This type is Sendable, but it cannot be proven due to limitations of the compiler, language, or frameworks.

Meaning 2 (the…other meaning):
This type is totally NOT Sendable, but I am way too tired to make it so. Please forgive me, those who suffer what I do today.

I fear in the not-to-distant future we will regret that these have the same spelling.

Show threadMatt MassicotteMar 20, 2024
@cocoaphony Many people will never accept a force-unwrap even though it is super easy to do. I agree it isn’t as impactful, not by a long shot. But I think many developers will just not accept unchecked in the same way.
Show threadChris WagnerMar 21, 2024
@mattiem @cocoaphony maybe it should be `@uncheckedSendable!` heh bangs are scary
Show threadMatt Massicotte

@cwagdev @cocoaphony ha!

But you know, I don't think you should be afraid of unchecked. I just think it always requires justification. Sometimes people are using it to "shut up the compiler" and I think that is something they will regret doing in the long run, even if it is really tempting right now.

Mar 21, 2024 at 2:58pmPhanpy
Show threadChris WagnerMar 21, 2024
@mattiem @cocoaphony I’d wager 90% of the usage is to shut up the compiler lol