[WIp] ALP encoder/decoder support#9372
Conversation
|
amaaazing |
|
@alamb I worked with codex on replicating the c++ implementation reviewing commit by commit. I'll do one final read myself, but this should be ready for initial review. |
|
Thank you -- I will put this on my short list to reivew I was out last week |
|
@devanbenz Sorry for taking so long to address your comments. I'll make sure to work on it this week! |
devanbenz
left a comment
There was a problem hiding this comment.
Comment about header regarding publication of spec.
|
Thanks @devanbenz, I've finally addressed your reviews! |
Please cargo fmt the code 🫡 |
|
|
Refactor: Pull common header structures into common module
|
here is another small proposed improvement |
Align structure names with spec
# Which issue does this PR close? - Related to #9372 # Rationale for this change Similarly to #9948. I ran into BitWriter as part of reviewing code from @sdf-jkl and wanted to document my findings (so I didn't have to re-read the code each time) - #9372 # What changes are included in this PR? Add docs # Are these changes tested? By CI # Are there any user-facing changes? No -- this is docs to an internal structure
# Which issue does this PR close? - Related to #9372 # Rationale for this change While reviewing the ALP implementation from @sdf-jkl , I ran into this struct which I haven't really used before. - #9372 Now that I have read it, I wanted to capture that information as doc comments (for my future self and hopefully for others) # What changes are included in this PR? Add documentation comments to `BitReader` # Are these changes tested? Just docs, # Are there any user-facing changes? Just docs on an internal struct,
# Which issue does this PR close? - Related to apache#9372 # Rationale for this change Similarly to apache#9948. I ran into BitWriter as part of reviewing code from @sdf-jkl and wanted to document my findings (so I didn't have to re-read the code each time) - apache#9372 # What changes are included in this PR? Add docs # Are these changes tested? By CI # Are there any user-facing changes? No -- this is docs to an internal structure
# Which issue does this PR close? - Related to apache#9372 # Rationale for this change While reviewing the ALP implementation from @sdf-jkl , I ran into this struct which I haven't really used before. - apache#9372 Now that I have read it, I wanted to capture that information as doc comments (for my future self and hopefully for others) # What changes are included in this PR? Add documentation comments to `BitReader` # Are these changes tested? Just docs, # Are there any user-facing changes? Just docs on an internal struct,
|
Thanks @sdf-jkl -- I will try and find tiume to review this (probably not until the weekend though as I have to sort out the next object store release before |
Which issue does this PR close?
Rationale for this change
check issue
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?