3 points | by cryptonector 2 days ago ago
2 comments
Lite^3 is a clever encoding for JSON data that is indexed as-encoded and is mutable in place.
Perhaps I should have posted this URI instead: https://lite3.io/design_and_limitations.html
Lite^3 deserves to be noticed by HN. u/eliasdejong (the author) posted it 23 days ago but it didn't get very far. I'm hoping this time it gets noticed.
The docs mention that space for overwritten variable-sized values in the buffer is not reclaimed:
The overridden space is never recovered, causing buffer size to grow indefinitely.
Lite^3 is a clever encoding for JSON data that is indexed as-encoded and is mutable in place.
Perhaps I should have posted this URI instead: https://lite3.io/design_and_limitations.html
Lite^3 deserves to be noticed by HN. u/eliasdejong (the author) posted it 23 days ago but it didn't get very far. I'm hoping this time it gets noticed.
The docs mention that space for overwritten variable-sized values in the buffer is not reclaimed:
Is the garbage at least zeroed? Otherwise seems like it could "leak" overwritten values when sending whole buffers via memcpy