-
Notifications
You must be signed in to change notification settings - Fork 72
Kick off discussion about extracting bit primitives #112
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
Conversation
Some thoughts: First off, I think the set of types is not sufficient. We're going to need to include (for example) the One concern is that this code uses some internal rustc features for efficiency purposes (in particular, we forbid indices from taking on any value greater than On the other hand, we probably don't want too many other consumers anyway, because that would imply a certain measure of stability and I'm not sure we're up to maintaining it, nor to making the API particularly nice. One reason I can see to do this, apart from providing general value to the ecosystem, is that it would help to support crates like chalk, polonius, and so forth, which wind up wanting some of this functionality. The other reason of course is that it enables people to maintain the crates with less overhead. On the other hand, it will make larger scale changes harder, as one must modify the crate first and then publish to crates.io and so forth. I guess one question for me is if we have other consumers in mind already. I should check whether (e.g.) chalk might actually make use of these types. |
We discussed this a bit on Zulip, and we had the idea that maybe we should start by just creating the crate in tree before we talk about moving it out of tree. Once the crate boundary is established, we can decide whether to pull it into a separate repository. I think this is a great first step, therefore I'm going to go ahead and close this issue in favor of that plan -- we can re-open once we have something concrete to talk about! |
Error: This repository is not enabled to use triagebot. Please let |
24 similar comments
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
23 similar comments
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Error: This repository is not enabled to use triagebot. Please let |
Woah, something seems to have upset triagebot. :) |
What the hell. |
It seems like this was reopened because triagebot was mad, if it was reopened on purpose please comment back on the issue. Trying to close it again ... |
This is my first contribution to rust, so feel free to point me to the right direction if I do something unconventionally.
Rust ticket: rust-lang/rust#50592
For context, data types I could find:
Decisions to be made:
@rfcbot merge