New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add "bitfield" to Cargo.toml keywords #308
Comments
I might have misunderstood deku's purpose. Is it really meant for any kind of bitfield? Comparing asm output of some bitfields implemented in deku vs other bitfield crates, deku produces 20x more code. When looking at could open another issue if you want |
Could you explain the nightly feature and what this would do? I'm not familiar and curious. |
@wcampbell0x2a it could call all those trait methods at compile time if possible and/or optimize them out: I'm not sure how
Then again, I might have mixed this up (even non-const stuff can get computed at compile time), so if someone wants to go at this, it's probably best to first try to put |
fyi: bitvec needs to use heavy usage of inline already to get decent performance: https://github.com/search?q=repo%3Aferrilab%2Fbitvec+inline&type=code |
This would make it easier to find, I only noticed this existed by reading bitvec docs.
Adding that word in the docs somewhere might help as well, either saying "you can use it like that" or specifying why it is different.
The text was updated successfully, but these errors were encountered: