aboutsummaryrefslogtreecommitdiff
path: root/crates/ide/src/markdown_remove.rs
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-06-21 14:41:27 +0100
committerGitHub <[email protected]>2021-06-21 14:41:27 +0100
commitb48aba009025701c4adb45e2042f0bcdb9d949a7 (patch)
tree9c311ee5e9058a3db66134368c8b84c30ed94f81 /crates/ide/src/markdown_remove.rs
parent4402f2b280f58896ed0696f4243d88a58fd970ca (diff)
parent8b77e2692cd97552b1b8d66eb51cec69695b3a5b (diff)
Merge #9227
9227: Add a config setting to disable the 'test' cfg in specified crates r=matklad a=lf- If you are opening libcore from rust-lang/rust as opposed to e.g. goto definition from some other crate which would use the sysroot instance of libcore, a `#![cfg(not(test))]` would previously have made all the code excluded from the module tree, breaking the editor experience. Core does not need to ever be edited with `#[cfg(test)]` enabled, as the tests are in another crate. This PR puts in a slight hack that checks for the crate name "core" and turns off `#[cfg(test)]` for that crate. Fixes #9203 Fixes #9226 Co-authored-by: Jade <[email protected]>
Diffstat (limited to 'crates/ide/src/markdown_remove.rs')
0 files changed, 0 insertions, 0 deletions