commit | 885954cb37e4551b2ed5dffd554d6f640abd7ad7 | [log] [tgz] |
---|---|---|
author | Jubilee <workingjubilee@gmail.com> | Wed Oct 30 14:01:37 2024 -0700 |
committer | GitHub <noreply@github.com> | Wed Oct 30 14:01:37 2024 -0700 |
tree | fd8a94fe636da217766e10020e5df18518a3e9cf | |
parent | 87f5047e646f0cfae25c953b70aa29f48f2e4edb [diff] | |
parent | e3b428c15aed3680e821bd4feb95cb3343987192 [diff] |
Rollup merge of #132210 - notriddle:notriddle/doctest-span-hack, r=GuillaumeGomez rustdoc: make doctest span tweak a 2024 edition change Fixes #132203 This is a compatibility hack, because I think the new behavior is better. When an A `include_str!` B, and B `include_str!` C, the path to C should be resolved relative to B, not A. That's how `include!` itself works, so that's how `include_str!` with should work.
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 check out the CONTRIBUTING.md or if you 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.