Skip to content
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

Key-value log passes correctness tests #23

Merged
merged 3 commits into from
Sep 1, 2017
Merged

Key-value log passes correctness tests #23

merged 3 commits into from
Sep 1, 2017

Conversation

matthewhammer
Copy link

@matthewhammer matthewhammer commented Sep 1, 2017

I feel fairly confident that the key value log is now implemented correctly, and would like to land this module into the dev and master branches, ideally. I'll start with this PR for dev.

Some things still to figure out: The "right way" for the code to choose these constants CHUNK_BITS and CHUNK_BITC. Ideally, we'd use associated constants of a (currently non-existent) type parameter, to impose zero runtime overhead for storing these constants in the data structure itself.

@matthewhammer
Copy link
Author

PS: This PR brings us very close to closing #20

@kyleheadley
Copy link
Member

Looks good to me.

Associated constants have landed in stable 1.20, so there's no reason not to use them. You can even define a default parameter for traits, as described here: rust-lang/reference#24

It looks like we're close to pushing our work into master. You'll have to show me how to make a overview issue to handle that.

@matthewhammer matthewhammer merged commit 7379093 into dev Sep 1, 2017
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.

2 participants