support bit fields for C interop
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 6.6k
- Forks
- 1.7k
- Avg merge
- 16h 14m
- Merged PRs (30d)
- 1
Description
Bitfields are commonly encountered when interacting with C code. Since many of the details of the behavior of bitfields are left to the implementation, it is hard to write cross-platform rust code that uses bitfields correctly. (Source: https://github.com/rust-lang/rfcs/pull/1449/)
Prior RFCs and other citations:
- https://github.com/rust-lang/rfcs/pull/1449
- This RFC was judged to be very-close to what we would want, but with certain specific details that needed to be included; a follow-up that takes a similar approach but addresses those questions would be welcome.
- https://github.com/rust-lang/rust/issues/8680
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading RFC 1449, its linked discussion about the details needing resolution, and rust-lang/rust issue 8680. The work is complete when a follow-up RFC defines a coherent approach to supporting C bitfields and addresses the cited concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100