mirror of
https://github.com/rust-lang/rust-analyzer.git
synced 2025-09-28 12:54:58 +00:00
Merge commit 'aa9bc86125
' into sync-from-ra
This commit is contained in:
parent
1570299af4
commit
c48062fe2a
598 changed files with 57696 additions and 17615 deletions
|
@ -97,7 +97,7 @@ pub use crate::{
|
|||
|
||||
/// Main entry point for completion. We run completion as a two-phase process.
|
||||
///
|
||||
/// First, we look at the position and collect a so-called `CompletionContext.
|
||||
/// First, we look at the position and collect a so-called `CompletionContext`.
|
||||
/// This is a somewhat messy process, because, during completion, syntax tree is
|
||||
/// incomplete and can look really weird.
|
||||
///
|
||||
|
@ -133,7 +133,7 @@ pub use crate::{
|
|||
///
|
||||
/// Another case where this would be instrumental is macro expansion. We want to
|
||||
/// insert a fake ident and re-expand code. There's `expand_speculative` as a
|
||||
/// work-around for this.
|
||||
/// workaround for this.
|
||||
///
|
||||
/// A different use-case is completion of injection (examples and links in doc
|
||||
/// comments). When computing completion for a path in a doc-comment, you want
|
||||
|
@ -243,7 +243,7 @@ pub fn resolve_completion_edits(
|
|||
config.prefer_no_std,
|
||||
)
|
||||
})
|
||||
.find(|mod_path| mod_path.to_string() == full_import_path);
|
||||
.find(|mod_path| mod_path.display(db).to_string() == full_import_path);
|
||||
if let Some(import_path) = import {
|
||||
insert_use::insert_use(&new_ast, mod_path_to_ast(&import_path), &config.insert_use);
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue