-
Notifications
You must be signed in to change notification settings - Fork 5
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
Consider using prefix code
and zigzag
encoding for variable-length integers
#8
Comments
Proposal: can we broaden this issue to discuss what variable-length integer encoding in general would be most appropriate? I was unfamiliar with zigzag encoding and what advantages it would have over the current method, so I searched for "leb128 vs zigzag". I found these two related discussions about LEB128 being used in WASM, both of which raised a number of points that seemed relevant to the topic: https://news.ycombinator.com/item?id=11263378 A quick summary of what stood out to me:
I have no strong opinions on any of this, and I do not know what the most relevant criteria are to decide on a varint encoding for muon anyway. But these points they seemed relevant enough to bring up (even if muon sticks to plain LEB128 you can at least say that you looked at alternatives, right?) PS: for anyone else unfamiliar with zigzag encoding, this blog and this SO question helped me out |
prefix code
and zigzag
encoding for variable-length integers
I think i'll give it another try |
No description provided.
The text was updated successfully, but these errors were encountered: