ddidderr/zstd-rs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(rust): document CDict initialization boundary

Browse Source 
Clarify that CDict initialization ordering and scalar publication now run in
Rust, while allocation, private dictionary loading, and match/workspace
callbacks remain C-owned.

Test Plan:
- git diff --cached --check
This commit is contained in:
ddidderr
2026-07-19 15:02:27 +02:00
parent 7775396fae
commit cc8cc47da7
1 changed files with 8 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
rust/README.md
+8 -7
View File
@@ -147,13 +147,14 @@ orchestration, sequence-store and block policy, external-producer invocation
and success-path validation, external-sequence-store reset, and success-path validation, external-sequence-store reset,
external-sequence/literals block loop, optional-format decompression loops, external-sequence/literals block loop, optional-format decompression loops,
block decoder wrappers, decompression result policy, and public end-of-frame block decoder wrappers, decompression result policy, and public end-of-frame
compression orchestration now run in Rust. CDict construction/lifecycle compression orchestration now run in Rust. CDict allocation/lifecycle
machinery, the private dictionary-content loader, reset policy, private machinery, private dictionary-content allocation/loading, reset policy,
CCtx/matchfinder/workspace operations, and codec/adaptive-policy callbacks private CCtx/matchfinder/workspace operations, and codec/adaptive-policy
remain in C. CDict-begin parameter selection, initialization ordering, and callbacks remain in C. CDict initialization ordering and scalar publication,
source-window policy now run in Rust behind a private-state bridge; its final CDict-begin parameter selection, initialization ordering, and source-window
C begin operation remains. The remaining C paths must move before the rewrite policy now run in Rust behind private-state bridges; their C callbacks and
is complete. final begin operation remain. The remaining C paths must move before the
rewrite is complete.
Keeping that boundary explicit prevents a passing hybrid build from being Keeping that boundary explicit prevents a passing hybrid build from being
mistaken for the final all-Rust result. mistaken for the final all-Rust result.