-
-
Notifications
You must be signed in to change notification settings - Fork 696
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
Isolating sstable and stacker in independant crates. #1718
Conversation
5a6dcb4
to
c7f6bdc
Compare
dddebc2
to
6cae790
Compare
Both crate will be used in the new (optional + dynamic) fastfield work.
1e45eac
to
59a11c5
Compare
59a11c5
to
44cdf14
Compare
/// | ||
/// The quirky API has the benefit of avoiding | ||
/// the computation of the hash of the key twice, | ||
/// or copying the key as long as there is no insert. | ||
pub struct TermHashMap { | ||
pub struct ArenaHashMap { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the new name is too generic, the implementation is very specific, mapping &[u8] keys to ids
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah... So Term
will soon be incorrect, as I use the stacker with field names as keys in dynamic fast fields.
I could have something like ArenaBytesHashMap
or something like this, but I think at this point ArenaHashMap
is ok.
Both crate will be used in the new (optional + dynamic) fastfield work.
Both crate will be used in the new (optional + dynamic) fastfield work.