You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
RFC 1444 was accepted a few weeks ago, bringing us actual real support for unions. Will libc grow to support for unions in its struct definitions?
The big issue I see for it is the RFC doesn't add unnamed unions, which covers most if not all of the unions we have in libc. At the same time, it'd be really great to not have to define the unions in client code, and to have libc's stronger testing applied to them.
The other issue I see is Rust version compatibility. I'll open another issue for that.
The text was updated successfully, but these errors were encountered:
Certainly! We may not be able to change existing types but we can certainly add more! This is mostly just covered by the version policy, so I'm gonna close in favor of that.
(also just waiting on unions to get implemented...)
I'd argue for a semver incompatible bump to include proper definitions, even for existing types. Depending on how various bitfield RFCs are going, this bump could perhaps wait to encompass both.
RFC 1444 was accepted a few weeks ago, bringing us actual real support for unions. Will libc grow to support for unions in its struct definitions?
The big issue I see for it is the RFC doesn't add unnamed unions, which covers most if not all of the unions we have in libc. At the same time, it'd be really great to not have to define the unions in client code, and to have libc's stronger testing applied to them.
The other issue I see is Rust version compatibility. I'll open another issue for that.
The text was updated successfully, but these errors were encountered: