multiboot2: foundation for mutable reference to tags #171
Conversation
This file contains 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
|
I'm still unsure but I think with this approach, we might have a less invasive approach while still having idiomatic Rust - What do you think, @YtvwlD ? |
|
oh, yes, this looks interesting (if it worked 🙃) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the foundation for a mutable boot information and another approach than #140. By using the
NonNullfacility, we can ensure that the compiler will not optimize away any mutable operations. I could not find a way to useUnsafeCellhere in a meaningful way.I think this approach has the advantage that the public API is barely changed - unlike in #140.