-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 loop
keyword from the language
#12975
Comments
cc #2233: Remove |
let mut a;
loop {
a = 1;
// ... break ...
}
do_something(a) is valid but the |
Language changes such as this require and RFC rather than an issue in the rust repository, I would recommend following the procedure over at https://github.com/rust-lang/rfcs. |
Also, we definitely cannot remove |
|
@alexcrichton Obviously requires an RFC. I'm much appreciate if someone has interest writing it. (I'm not a native-english user, too hard to write it for me, sorry.) @pnkfelix @Thiez We can do more if we want to remove or replace it. |
Piggybacks on while-expr parsing the same way as `while let` to recognize `while true` and call the existing `loop` parsing code. Fixes rust-lang#12975.
I'd like to take up replacing the I have a rough pass at an RFC up here: I am willing to do the work of replacing all occurrences of Also, if anyone can point me to an easy way to mechanically transform Rust source, I might make a tool to help with migration. Thanks! |
@jkleint thank you for working on this! |
…ievink fix: record completion filtering close rust-lang#12975
loop
loops can be removed, because it doesn't do any special jobs thanwhile true {}
(which maybe simplified towhile { }
).Do we really need two similar loops? (loop VS. while)
The text was updated successfully, but these errors were encountered: