Persist Partitions into a thread_local variable and remove PartitionsMaybe #6298
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.
Motivation
Partitions
is already "global", in the sense that even in unit tests (ic_stable_structures::VectorMemory) is anRc<RefCell<Vec<u8>>>
, and operations to various memory partitions read/write from/to the bytes owned by theRc
. Therefore, it makes sense forPartitions
to be athread_local!
variable. On the other hand,PartitionsMaybe
is only useful when there can be 2 cases (raw/managed memory), which is no longer the case after the migration.Changes
PARTITIONS
thread_local
variable and add accessorsPartitionsMaybe
and simplify dead codeTests
N/A since it's mostly trivial refactoring. Tests under
rs/backend/src/state/tests.rs
should cover the code changed in this PR.Related PRs
Previous | Next