cl-messagepack
cl-messagepack copied to clipboard
mbrezu
A Common Lisp implementation of Message Pack
This PR: - uses ieee-floats encode/decode. - conforms to specs. encoding extensions `(#xD4 to #xD8, and #xC7 to #xC9)` - conforms to specs. encoding binary array. - conforms to specs....
Commit https://github.com/mbrezu/cl-messagepack/commit/b305346a719eb766ce71da4603332ca4b9f8220d changed the initarg for defined extension types from `:id` to `messagepack-sym:id` and is thus not backwards compatible. This caused a brief headache that could've been avoided by either...
The change to the :initarg of extension-type from **'id** to **:id** is not compatible with the tests extension-types-encoding and extension-types, which both pass **'messagepack-sym:id** to make-instance with the extension-type. Also...
According to the [msgpack website instructions](https://github.com/msgpack/website/blob/master/README.md#how-to-list-up-your-project-on-msgpackorg), this involves: 1. Add the keyword msgpack.org[ProjctName] to description of your github repository. ProjectName is typically name of a programming language such as ruby...
As far as I have been able to understand, cl-messagepack's current implementation of extensions doesn't allow you to encode arbitrary data, associate it with some type, and then communicate this...
Is this version 5 compatible? I plan on using this library and I want to know if it can differentiate between strings and binary values. If so I plan on...
Hello, I would like to request more benchmarks and tests to be added. I want to use this library, but I need to make sure it's stable in edgecases. For...
