commit | 6f6b03f9de783f91456080b3f6adc8d92903c1b0 | [log] [tgz] |
---|---|---|
author | bors <bors@rust-lang.org> | Sun Mar 24 18:17:36 2024 +0000 |
committer | bors <bors@rust-lang.org> | Sun Mar 24 18:17:36 2024 +0000 |
tree | 05d808312dc024d8a211e9536a8ee30e9cc0fb31 | |
parent | 3dfd4c1f4c955e13d5936a3ffa2a19661c97cd07 [diff] | |
parent | 2dfe7de8b66c17b3f9025766597b8399394527b8 [diff] |
Auto merge of #16935 - Nilstrieb:dont-panic, r=HKalbasi Handle panicking like rustc CTFE does Instead of using `core::fmt::format` to format panic messages, which may in turn panic too and cause recursive panics and other messy things, redirect `panic_fmt` to `const_panic_fmt` like CTFE, which in turn goes to `panic_display` and does the things normally. See the tests for the full call stack. The tests don't work yet, I probably missed something in minicore. fixes #16907 in my local testing, I also need to add a test for it
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.