✨ Add uninitialized state for fields
#792
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Problem: - Sometimes it is useful to use fields that overlap: for instance to be able to inspect individual bits _and_ have an overlapping field that represents the set of bits as a whole. In these cases it is useful at construction time to leave such an overlapping field uninitialized so that we don't have a scenario where one initialization overwrites another. Solution: - Allow a field to be marked as `uninitialized` so that on construction it won't potentially clobber other fields. Note: - The difference between `without_default` and `uninitialized` is that a field marked `without_default` must still be given a value at construction time.
mjcaisse-intel
approved these changes
Nov 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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:
Solution:
uninitializedso that on construction it won't potentially clobber other fields.Note:
without_defaultanduninitializedis that a field markedwithout_defaultmust still be given a value at construction time.