mirror of
https://github.com/rust-lang/rust-analyzer
synced 2025-01-12 13:18:47 +00:00
Delete old issues from GitHub's bug report template
This commit is contained in:
parent
803ff2e55e
commit
f5c6c43bd1
1 changed files with 3 additions and 6 deletions
9
.github/ISSUE_TEMPLATE/bug_report.md
vendored
9
.github/ISSUE_TEMPLATE/bug_report.md
vendored
|
@ -13,12 +13,9 @@ Forum for questions: https://users.rust-lang.org/c/ide/14
|
||||||
|
|
||||||
Before submitting, please make sure that you're not running into one of these known issues:
|
Before submitting, please make sure that you're not running into one of these known issues:
|
||||||
|
|
||||||
1. local imports (`use` statements) don't work: #1165
|
1. on-the-fly diagnostics are mostly unimplemented (`cargo check` diagnostics will be shown when saving a file)
|
||||||
2. local items don't work: #1559
|
2. some settings are required for procedural macro and build script support (`rust-analyzer.cargo.loadOutDirsFromCheck`, `rust-analyzer.procMacro.enable`): #6448
|
||||||
3. on-the-fly diagnostics are mostly unimplemented (`cargo check` diagnostics will be shown when saving a file)
|
3. some platform-specific imports are not resolved: #6038
|
||||||
4. some settings are required for procedural macro and build script support (`rust-analyzer.cargo.loadOutDirsFromCheck`, `rust-analyzer.procMacro.enable`): #6448
|
|
||||||
5. some platform-specific imports are not resolved: #6038
|
|
||||||
6. the official `rust-lang.rust` VS Code extension conflicts with `rust-analyzer`: #6463
|
|
||||||
|
|
||||||
Otherwise please try to provide information which will help us to fix the issue faster. Minimal reproducible examples with few dependencies are especially lovely <3.
|
Otherwise please try to provide information which will help us to fix the issue faster. Minimal reproducible examples with few dependencies are especially lovely <3.
|
||||||
-->
|
-->
|
||||||
|
|
Loading…
Reference in a new issue