Parker Timmerman

Because Strings encoded in a proto message should be UTF8, I added a feature flag `zero_copy_string_no_utf8_check`, to skip utf8 validation, when using zero-copy strings. Using this flag, we get performance...

Update: I have a WIP change internally at Dropbox to migrate `pb-jelly-svc` to use futures03. We'll work on getting that open sourced soon, and then we'll need to integrate with...

@SkamDart thanks for the reminder, I got caught up in end of the year stuff but I'll try and make some progress here this week or next

Update, I haven't forgotten about this, but haven't found the time to get it done yet. Thanks for being patient, and sorry to anyone who is waiting 🙂

This may have been closed by #26

#70 adds a QualityValue type, it could totally be reworked if necessary, and open to comments on it 🙂

Great point, lets do it! What do you think about supporting the following 6 APIs: 1. `from_utf16(...)` (native endianness) 2. `from_utf16_lossy(...)` (native endianness) 3. `from_utf16_be(...)` 4. `from_utf16_be_lossy(...)` 5. `from_utf16_le(...)` 6....

Side note: looks like @CAD97 has a PR to introduce this to the stdlib too! https://github.com/rust-lang/rust/pull/95967

Also cc @NobodyXu, any thoughts here?

Hey @NobodyXu! Very sorry I didn't respond to this earlier. I'm open to using `kani`, would you be able to put up a proof of concept PR?