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
moonheart08 opened this issue
Oct 5, 2018
· 4 comments
Labels
needs-rfcThis change is large or controversial enough that it should have an RFC accepted before doing it.T-langRelevant to the language team, which will review and decide on the PR/issue.
LLVM itself supports arbitrary bitlength integers, however Rust does not. This would be useful for some less common, but still fairly normal cases, like 24-bit integers for emulating CPUs like the MC68000 (Some models use 24-bit address busses instead of 32-bit), or for memory constrained systems where you need all the space you can get, and as such packed bitfields are the best for storing data.
The text was updated successfully, but these errors were encountered:
estebank
added
the
T-lang
Relevant to the language team, which will review and decide on the PR/issue.
label
Jan 19, 2019
jonas-schievink
added
the
needs-rfc
This change is large or controversial enough that it should have an RFC accepted before doing it.
label
Jul 1, 2021
Does it make sense to make a full featured PoC crate for integers of any size (<=128) and eventually merge into the compiler? Or something like that should be built directly inside of rustc from the ground up?
needs-rfcThis change is large or controversial enough that it should have an RFC accepted before doing it.T-langRelevant to the language team, which will review and decide on the PR/issue.
LLVM itself supports arbitrary bitlength integers, however Rust does not. This would be useful for some less common, but still fairly normal cases, like 24-bit integers for emulating CPUs like the MC68000 (Some models use 24-bit address busses instead of 32-bit), or for memory constrained systems where you need all the space you can get, and as such packed bitfields are the best for storing data.
The text was updated successfully, but these errors were encountered: