Add sendable conformance to appropriate types

[jmjauer]

Add Sendable conformance to appropriate types would allow to enabled additional safety checks at compile time. Without it, developers have to guess whether a type is Sendable or not.

[Sajjon]

Ah the by Github listed "mention" was a red herring, I was trying to write "amount: 150" using pound sign, which was a silly thing to do, since I forgot GH lists is a references... Sorry for misleading "mention".

But YES I agree Sendable would be great to have, when safe to mark as such!

[Sajjon]

I see no reason for ECDSASignature to not be Sendable, nor any reason for why all PublicKeys cannot be Sendable.

[Lukasa]

Huh, I thought I commented on this. Regardless: we've heard this feedback internally, thanks for providing it!

[Sajjon]

@Lukasa mind if I submit a PR making PublicKeys Equatable? I know different topic... but IMO falls under non dangerous protocol conformances helping devs :)

[Lukasa]

This is a good suggestion, thanks. As this affects the common API layer between CryptoKit and Swift Crypto, while you can make a PR we will be unable to merge it until an equivalent change ships in CryptoKit.

[jmjauer]

Are the people who maintain CryptoKit the same ones who maintain Swift Crypto - or should I post this suggestion somewhere else?

[Lukasa]

I'm afraid that's not something I can get into detail about, but I will say that filing a request using Feedback Assistant is always valuable.