-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Implement simple, unstable lint to suggest turning closure-of-async-block into async-closure #127097
Conversation
This comment has been minimized.
This comment has been minimized.
284d3cf
to
987fd17
Compare
This comment has been minimized.
This comment has been minimized.
987fd17
to
acc13e2
Compare
r? @oli-obk |
@bors r+ rollup |
…, r=oli-obk Implement simple, unstable lint to suggest turning closure-of-async-block into async-closure We want to eventually suggest people to turn `|| async {}` to `async || {}`. This begins doing that. It's a pretty rudimentary lint, but I wanted to get something down so I wouldn't lose the code. Tracking: * rust-lang#62290
Rollup of 3 pull requests Successful merges: - rust-lang#127097 (Implement simple, unstable lint to suggest turning closure-of-async-block into async-closure) - rust-lang#127153 (Initial implementation of anonymous_pipe API) - rust-lang#127572 (Don't mark `DEBUG_EVENT` struct as `repr(packed)`) r? `@ghost` `@rustbot` modify labels: rollup
☀️ Test successful - checks-actions |
Finished benchmarking commit (9b00430): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesResults (secondary 3.9%)This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.
Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 703.504s -> 703.344s (-0.02%) |
We want to eventually suggest people to turn
|| async {}
toasync || {}
. This begins doing that. It's a pretty rudimentary lint, but I wanted to get something down so I wouldn't lose the code.Tracking:
#![feature(async_closure)]
(RFC 2394 / RFC 3668) #62290