Matt Gadda

I'm not sure that suppressing the errors is necessarily the best solution. One might want to know, for instance, about truly unknown or unused fragments, not just fragments from other...

@a2 I just stumbled across this ticket. I've actually been working on an implementation of a swift Encoder/Decoder for MessagePack over the weekend. It's not quite ready to be published...

Sorry, I didn't mean to be unclear. Yes, it's based on (i.e. dependent upon) your MessagePack.swift. And in terms of structure it closely follows the patterns established in `JSONEncoder/Decoder.swift` and...

I could go either way. Let me just finish up the implementation and then we can figure out where it should live.

Oh, that’s too bad. Seems like i was too slow! The implementation is nearly complete now. It too follows the same patterns shown in JSONEncoder.swift and is of course quite...

@andrew-eng I'm not a lawyer of course. And perhaps there's case to be made that the protocol-based design of Codable basically requires that the code look pretty close to what...

@andrew-eng I also ended up abandoning this pure swift implementation because it was far too slow for my needs. I ended up using the C-based https://github.com/camgunz/cmp which was many orders...

This still seems to be an issue, whether it's caused by Cargo Check or Clippy or not. It occurs in RustRover as well.

This is broken even when it's not installed as a development dependency.

Also, this is resolved in v1.1.3. @WaldoJeffers: can v1.1.3 be published to npm? It seems like this project is in a non-functional state (on macos at least) until then.