Skip to content

Conversation

@chrysn
Copy link
Member

@chrysn chrysn commented Oct 3, 2022

Given that this introduces yet another round of "signed vs unsigned char" errors on ARM architectures, this probably needs to sit and wait for a large breaking change. It's probably worth just biting through that once...

chrysn added 3 commits October 3, 2022 23:18
As the types re-exported from there are aliases to the native types (i8
etc) and not newtypes, they can compatibly be replaced with their
now-stdlib definitions.
Now that a recent change made 1.64 mandatory, this can just as well be
done now.
@chrysn
Copy link
Member Author

chrysn commented Oct 3, 2022

Seems like the type drama in the tests was "just" caused by having some dependencies not updated (falling back to older versions).

There might still be flip-flopping (cty on ARM has c_char = u8, core::ffi has c_char = i8), but given that all Rust code must support either already anyway, maybe it's not even a breaking change in some sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants