-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Change f16
and f128
clippy stubs to be nonpanicking
#123087
Conversation
Some changes occurred in src/tools/clippy cc @rust-lang/clippy |
rustbot has assigned @Mark-Simulacrum. Use |
@rustbot label +A-clippy r? clippy |
Cc @matthiaskrgr since you were looking at this recently Hey looks like you're on the clippy team too if you want to review :) |
f16
and f128
clippy stubs to be nonpanicking
@rustbot label +F-f16_and_f128 |
015538f
to
fcad3ca
Compare
Thanks @blyxyas, are you able to r+ or waiting for a second look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was waiting for Fred to review it, but I mean, it's a very small change. I'll just r+ this
(I'll also make a personal note to fix this once f16/f128 is stabilized)
Just a little thing, I wouldn't want to cause a bug because of time-mismatch
It turns out there is a bit of a circular dependency - I cannot add anything to `core` because Clippy fails, and I can't actually add correct Clippy implementations without new implementations from `core`. Change some of the Clippy stubs from `unimplemented!` to success values and leave a FIXME in their place to mitigate this. Fixes <rust-lang#122587>
fcad3ca
to
2cfd532
Compare
Much appreciated, I made the requested tweaks |
@bors r+ |
…bs, r=blyxyas Change `f16` and `f128` clippy stubs to be nonpanicking It turns out there is a bit of a circular dependency - I cannot add anything to `core` because Clippy fails, and I can't actually add correct Clippy implementations without new implementations from `core`. Change some of the Clippy stubs from `unimplemented!` to success values and leave a FIXME in their place to mitigate this. Fixes <rust-lang#122587>
…iaskrgr Rollup of 9 pull requests Successful merges: - rust-lang#108675 (Document `adt_const_params` feature in Unstable Book) - rust-lang#122120 (Suggest associated type bounds on problematic associated equality bounds) - rust-lang#122589 (Fix diagnostics for async block cloning) - rust-lang#122835 (Require `DerefMut` and `DerefPure` on `deref!()` patterns when appropriate) - rust-lang#123049 (In `ConstructCoroutineInClosureShim`, pass receiver by mut ref, not mut pointer) - rust-lang#123055 (enable cargo miri test doctests) - rust-lang#123057 (unix fs: Make hurd using explicit new rather than From) - rust-lang#123087 (Change `f16` and `f128` clippy stubs to be nonpanicking) - rust-lang#123103 (Rename `Inherited` -> `TypeckRootCtxt`) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#123087 - tgross35:clippy-f16-f128-check-stubs, r=blyxyas Change `f16` and `f128` clippy stubs to be nonpanicking It turns out there is a bit of a circular dependency - I cannot add anything to `core` because Clippy fails, and I can't actually add correct Clippy implementations without new implementations from `core`. Change some of the Clippy stubs from `unimplemented!` to success values and leave a FIXME in their place to mitigate this. Fixes <rust-lang#122587>
It turns out there is a bit of a circular dependency - I cannot add anything to
core
because Clippy fails, and I can't actually add correct Clippy implementations without new implementations fromcore
.Change some of the Clippy stubs from
unimplemented!
to success values and leave a FIXME in their place to mitigate this.Fixes #122587