Skip to content

Conversation

@danlarkin
Copy link
Contributor

No description provided.

@danlarkin danlarkin requested review from jmoniatte and kingcu June 8, 2022 23:47
Copy link

@jmoniatte jmoniatte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Besides "what's up with all those .rs files?", I am unfortunately not able to provide much feedback. The ruby code and API look very good to me though, thanks Dan!

I wanted to request a few examples in README.md, but realized that the spec files can be used for that.

jmoniatte and others added 14 commits April 14, 2023 16:31
This fixes a couple bugs that could have been caused by failed
writes. Previously, if a write failed (however unlikely that is) then
the `prev` field in the encoder would still have been changed, and so
future writes would have been corrupted. The same is true for updating
the presence column - now it only happens after the write succeeds.
Wrapping add/sub is the default in release mode, so this change has no
effect for production builds. But in debug mode, checked math is the
default, so this change allows the roundtrip integration tests to run
then too.
This commit doesn't change the F64 Encoder, even though it uses
write_i64. Those changes will be in the next commit.
The F64 Encoder can't accurately store the entire range of 64-bit
floating point numbers, since it's basically a fixed point
system. This change will cause it to return an error when there isn't
enough space to store the value it's been asked to encode.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants