-
Notifications
You must be signed in to change notification settings - Fork 13k
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
Remove under-used ImplPolarity enum #80825
Remove under-used ImplPolarity enum #80825
Conversation
499e65f
to
28e8daf
Compare
Could the similar |
The only one we seem to interact with is |
What does an impl polarity of I don't think it's clear at all that |
It's treated as "non-negative impl". Which is why I turned it into a boolean.
If you prefer. I think it's a bit too much considering how little use of it we make. Don't you confirm your choice? ;) |
28e8daf
to
d6c35b0
Compare
After a talk, we agreed on keeping the boolean but to rename the field from |
d6c35b0
to
34d128a
Compare
r=me with CI passing |
@bors: r=jyn514 |
📌 Commit 34d128a has been approved by |
…repetita, r=jyn514 Remove under-used ImplPolarity enum It doesn't make much sense to have an enum with only two possible values and to store it inside an `Option` in my opinion when you can do all the same with a simple boolean. I don't expect any chances, performance or RSS usage wise. r? `@jyn514`
Rollup of 9 pull requests Successful merges: - rust-lang#79502 (Implement From<char> for u64 and u128.) - rust-lang#79968 (Improve core::ptr::drop_in_place debuginfo) - rust-lang#80774 (Fix safety comment) - rust-lang#80801 (Use correct span for structured suggestion) - rust-lang#80803 (Remove useless `fill_in` function) - rust-lang#80820 (Support `download-ci-llvm` on NixOS) - rust-lang#80825 (Remove under-used ImplPolarity enum) - rust-lang#80850 (Allow #[rustc_builtin_macro = "name"]) - rust-lang#80857 (Add comment to `Vec::truncate` explaining `>` vs `>=`) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
It doesn't make much sense to have an enum with only two possible values and to store it inside an
Option
in my opinion when you can do all the same with a simple boolean. I don't expect any chances, performance or RSS usage wise.r? @jyn514