This repository has been archived by the owner on Jan 22, 2025. It is now read-only.
Refactors unsafe
out of CacheHashDataFile's header
#33270
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
We use
unsafe
blocks to read/write data in the various accounts hash files. That's not always needed.The
Header
type for cache hash data files is written-to and read-from disk, and we useunsafe
blocks for that. But we don't need to.Summary of Changes
Derive
Pod
forHeader
and refactor all of itsunsafe
blocks to usebytemuck
.