Skip to content
This repository has been archived by the owner on Mar 11, 2019. It is now read-only.

msgpack: Improvements and fixes for the unpacker #38

Merged
merged 2 commits into from
Aug 16, 2016

Conversation

arteymix
Copy link
Collaborator

I fixed the unpacker (streaming & non-streaming). I did not test them earlier.

I plan to write a small integration library to have convenient I/O streams upon that.

I wrote a small testsuite and if you're interested, I'll send another PR. It's really easy to write with Meson and it would be a good combination with #34.

Add a constructor to 'Unpacked' to call 'msgpack_unpacked_init'.

Let 'off' be 'null' by default in 'Unpacked.next'.

Add 'buffer_consumed' to 'Unpacked' which has to be invoked once we
write to 'buffer' with the number of bytes written.

Make 'data' in 'Unpacker' return an unowned 'Object' since it is held by
the unpacker.
@nemequ nemequ merged commit c345a3a into nemequ:master Aug 16, 2016
@nemequ
Copy link
Owner

nemequ commented Aug 16, 2016

Merged, thanks.

Not sure about the test suite… i want to keep this repo lean for people who are using it as a submodule/subtree.

@arteymix
Copy link
Collaborator Author

I understand. I'll add it in the integration library instead and send improvements/fixes upstream.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants