You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit da48008
Browse filesBrowse the repository at this point in the historyBrowse files
## Summary
`InitializedRow::fill` could return a token for an empty subslice,
allowing a safe callback to leave its output row uninitialized. Dense
execution could then publish that storage.
## Changes
Makes `fill` unsafe and requires the entire current callback's row to
remain initialized until that callback returns its token. Tightens the
corresponding `InitializedElement::write` contract and updates callers
and consumer safety comments. Retains ordinary, empty, zero-width, and
partially valid output coverage. Error and unwind abandonment remain
unchanged.
Reviewed the complete diff with `rust-style`. The commit hook ran `cargo
+nightly fmt --all -- --check` and reported formatting changes, which
were applied manually without rerunning the check. Tests, doctests,
builds, Clippy, and benchmarks were not run, following AGENTS.md. No
reproduction read uninitialized memory.
## API Changes
`InitializedRow::fill` now requires an explicit unsafe operation.
---------
Signed-off-by: "Connor Tsui" <[email protected]>
0 commit comments