-
Notifications
You must be signed in to change notification settings - Fork 259
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
Improve lookup table pattern use in profiles. #592
Conversation
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.
Added some docstring nits for consistency
Co-authored-by: Christos Kalkanis <[email protected]>
Co-authored-by: Christos Kalkanis <[email protected]>
Co-authored-by: Christos Kalkanis <[email protected]>
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 like the clarity of the renames
Co-authored-by: Christos Kalkanis <[email protected]>
Co-authored-by: Christos Kalkanis <[email protected]>
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.
LGTM. Nits (that could be addressed in follow-up PRs)
- Why
int32
instead ofuint32
for the indexes? I'd prefer the latter, but don't feel strongly. key_strindex
andlink_index
feels inconsistent. My preference would bekey_string_index
(same for other string indexes)
This has the required number of approvals. The rules require that we keep it open for 2 days since the last substantial change before merging. I will merge after that. |
uint32 has the same problem as int64 - it can hold values that don't map cleanly to the signed 32 bit array range in Java. It would express intent more clearly, but potentially cause more headaches for implementers. |
All comments must be resolved before we can merge. |
Based on implementation experience with the draft version of the profiles spec, the use of lookup tables for storing values is space efficient but not particularly user friendly. This change makes improvements by changing field names to clarify their role in the pattern and changing their data types to better accommodate their use in languages limited to 32 bit array indexing e.g. Java.