Make some new libctru types opaque #218
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
This fixes an issue where Rust doesn't allow `#[repr(packed)]` structs to transitively contain `#[repr(align)]` structs due to differing behavior between gcc and msvc toolchains.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
A new version of libctru was released a few days ago and it added some structs that
bindgenends up choking on. It turns out that Rust doesn't allow#[repr(packed)]structs to transitively contain#[repr(align)]structs due to differing behavior between gcc and msvc toolchains. There is an RFC in the works to find a long-term solution to this issue, but in the meantime we can work around the problem by just treating the problematic types as opaque blobs of bytes.