| commit | 05666441bafd6010787a4097a6bd44266ad21018 | [log] [tgz] |
|---|---|---|
| author | bors <bors@rust-lang.org> | Sun Sep 17 17:53:15 2023 +0000 |
| committer | bors <bors@rust-lang.org> | Sun Sep 17 17:53:15 2023 +0000 |
| tree | 31b12431ea791129fc4331a588f91358bcfccfad | |
| parent | 9d0ccf01a16f4ab72417a804c5a7414f312d95a0 [diff] | |
| parent | a961068504de97fca810d766d72a6ee913899a6e [diff] |
Auto merge of #15625 - jDomantas:domantas/fix-15623, r=HKalbasi fix: Don't skip closure captures after let-else As I understand that `return` was left there by accident. It caused capture analysis to skip the rest of the block after a let-else, and then missed captures caused incorrect results in borrowck, closure hints, layout calculation, etc. Fixes #15623 I didn't understand why I using the example from #15623 as-is doesn't work - I don't get the warnings unless I remove the `call_me()` call, even on the same commit as my own RA version which does show those warnings.
rust-analyzer is a modular compiler frontend for the Rust language. It is a part of a larger rls-2.0 effort to create excellent IDE support for Rust.
https://rust-analyzer.github.io/manual.html#installation
If you want to contribute to rust-analyzer or are just curious about how things work under the hood, check the ./docs/dev folder.
If you want to use rust-analyzer's language server with your editor of choice, check the manual folder. It also contains some tips & tricks to help you be more productive when using rust-analyzer.
See the corresponding sections of the manual.
For usage and troubleshooting requests, please use “IDEs and Editors” category of the Rust forum:
https://users.rust-lang.org/c/ide/14
For questions about development and implementation, join rust-analyzer working group on Zulip:
https://rust-lang.zulipchat.com/#narrow/stream/185405-t-compiler.2Frust-analyzer
rust-analyzer is primarily distributed under the terms of both the MIT license and the Apache License (Version 2.0).
See LICENSE-APACHE and LICENSE-MIT for details.