@@ -83,27 +83,27 @@ use crate::{
83
83
// NOTE: currently, if an assoc item comes from a trait that's not currently imported, and it also has an unresolved and/or partially-qualified path,
84
84
// no imports will be proposed.
85
85
//
86
- // . Fuzzy search details
86
+ // #### Fuzzy search details
87
87
//
88
88
// To avoid an excessive amount of the results returned, completion input is checked for inclusion in the names only
89
89
// (i.e. in `HashMap` in the `std::collections::HashMap` path).
90
90
// For the same reasons, avoids searching for any path imports for inputs with their length less than 2 symbols
91
91
// (but shows all associated items for any input length).
92
92
//
93
- // . Import configuration
93
+ // #### Import configuration
94
94
//
95
95
// It is possible to configure how use-trees are merged with the `imports.granularity.group` setting.
96
96
// Mimics the corresponding behavior of the `Auto Import` feature.
97
97
//
98
- // . LSP and performance implications
98
+ // #### LSP and performance implications
99
99
//
100
100
// The feature is enabled only if the LSP client supports LSP protocol version 3.16+ and reports the `additionalTextEdits`
101
101
// (case-sensitive) resolve client capability in its client capabilities.
102
102
// This way the server is able to defer the costly computations, doing them for a selected completion item only.
103
103
// For clients with no such support, all edits have to be calculated on the completion request, including the fuzzy search completion ones,
104
104
// which might be slow ergo the feature is automatically disabled.
105
105
//
106
- // . Feature toggle
106
+ // #### Feature toggle
107
107
//
108
108
// The feature can be forcefully turned off in the settings with the `rust-analyzer.completion.autoimport.enable` flag.
109
109
// Note that having this flag set to `true` does not guarantee that the feature is enabled: your client needs to have the corresponding
0 commit comments