-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update impls.html #56
Conversation
Add https://github.com/fxamacker/cbor and remove incomplete implementation
So what is the state of 2tvenom's implementation? |
According to github, it seems unmaintained for the last 2 years and has at least these known issues (from the readme):
|
Yes, I saw that. Is the other implementation you are referencing compatible (at least vaguely)?
Neither does the fxamacker one, AFACS.
OK
That is a limitation.
Does the fxamacker one? Just trying to find out if the 2tvenom one should stay in or is wholeheartedly replaced. Maybe I should contact 2tvenom. |
Would say so. Same API design.
I'll ask him. |
Hi, I maintain fxamacker/cbor. Thanks for considering it.
My decoder ignores tags but decodes tagged data. Encoder does not support tags yet.
My decoder supports indefinite-length values for bytes/strings/arrays/maps. Encoder doesn't support it yet. By comparison, 2tvenom/cbor doesn't appear to support decoding indefinite-length values, based on a quick look at 2tvenom/cbor/cbor.go. Thanks again, Faye |
Since the last release it does. https://github.com/fxamacker/cbor/releases/tag/v0.2.0 |
@cabo Do you expect me to change this pull request in any way? I am happy to incorporate any feedback. |
I released fxamacker/cbor v1.0. Changes are summarized here. Please let me know if you have any questions or suggestions. Thanks. |
@cabo The mentioned cbor implementation evolved rapidly and is now in a state that I recommend adding to the website. The README now covers information to all limitations and there is a roadmap as well. |
@cabo Hello! I released fxamacker/cbor 2.1. It is a fast, safe, and full-featured generic CBOR encoder and decoder in Go. Compared to the best Go impl listed on cbor.io, it is more full-featured, faster, uses less memory, produces smaller data, and produces smaller apps (see comparisons below). Please let me know if there's anything that's preventing fxamacker/cbor from being listed. I can provide a PR if you prefer not to replace an existing Go impl. Thanks! fxamacker/cbor 2.1 supports:
More info at: Encoder and Decoder Options, and Standards Here's how fxamacker/cbor compares to the best Go library currently listed on cbor.io using using test data from RFC 8392 A.1 for speed and memory comparisons. Safety Comparison
Compiled Program Size Comparison
Speed Comparison (lower ns/op is better)
Memory Comparison (lower numbers are better)
|
Thank you for this interesting implementation, and apologies for my glacial speed merging the pointer to this. |
Add https://github.com/fxamacker/cbor and remove incomplete implementation