mirror of
https://github.com/rust-lang/rust-analyzer
synced 2025-01-06 18:28:51 +00:00
c3a4c4429d
This introduces the new type -- Semantics. Semantics maps SyntaxNodes to various semantic info, such as type, name resolution or macro expansions. To do so, Semantics maintains a HashMap which maps every node it saw to the file from which the node originated. This is enough to get all the necessary hir bits just from syntax.
79 lines
2.7 KiB
Rust
79 lines
2.7 KiB
Rust
//! FIXME: write short doc here
|
|
|
|
mod completion_item;
|
|
mod completion_context;
|
|
mod presentation;
|
|
|
|
mod complete_dot;
|
|
mod complete_record_literal;
|
|
mod complete_record_pattern;
|
|
mod complete_pattern;
|
|
mod complete_fn_param;
|
|
mod complete_keyword;
|
|
mod complete_snippet;
|
|
mod complete_path;
|
|
mod complete_scope;
|
|
mod complete_postfix;
|
|
mod complete_macro_in_item_position;
|
|
mod complete_trait_impl;
|
|
|
|
use ra_ide_db::RootDatabase;
|
|
|
|
#[cfg(test)]
|
|
use crate::completion::completion_item::do_completion;
|
|
use crate::{
|
|
completion::{
|
|
completion_context::CompletionContext,
|
|
completion_item::{CompletionKind, Completions},
|
|
},
|
|
FilePosition,
|
|
};
|
|
|
|
pub use crate::completion::completion_item::{
|
|
CompletionItem, CompletionItemKind, InsertTextFormat,
|
|
};
|
|
|
|
/// 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.
|
|
/// This is a somewhat messy process, because, during completion, syntax tree is
|
|
/// incomplete and can look really weird.
|
|
///
|
|
/// Once the context is collected, we run a series of completion routines which
|
|
/// look at the context and produce completion items. One subtlety about this
|
|
/// phase is that completion engine should not filter by the substring which is
|
|
/// already present, it should give all possible variants for the identifier at
|
|
/// the caret. In other words, for
|
|
///
|
|
/// ```no-run
|
|
/// fn f() {
|
|
/// let foo = 92;
|
|
/// let _ = bar<|>
|
|
/// }
|
|
/// ```
|
|
///
|
|
/// `foo` *should* be present among the completion variants. Filtering by
|
|
/// identifier prefix/fuzzy match should be done higher in the stack, together
|
|
/// with ordering of completions (currently this is done by the client).
|
|
pub(crate) fn completions(db: &RootDatabase, position: FilePosition) -> Option<Completions> {
|
|
let ctx = CompletionContext::new(db, position)?;
|
|
|
|
let mut acc = Completions::default();
|
|
|
|
complete_fn_param::complete_fn_param(&mut acc, &ctx);
|
|
complete_keyword::complete_expr_keyword(&mut acc, &ctx);
|
|
complete_keyword::complete_use_tree_keyword(&mut acc, &ctx);
|
|
complete_snippet::complete_expr_snippet(&mut acc, &ctx);
|
|
complete_snippet::complete_item_snippet(&mut acc, &ctx);
|
|
complete_path::complete_path(&mut acc, &ctx);
|
|
complete_scope::complete_scope(&mut acc, &ctx);
|
|
complete_dot::complete_dot(&mut acc, &ctx);
|
|
complete_record_literal::complete_record_literal(&mut acc, &ctx);
|
|
complete_record_pattern::complete_record_pattern(&mut acc, &ctx);
|
|
complete_pattern::complete_pattern(&mut acc, &ctx);
|
|
complete_postfix::complete_postfix(&mut acc, &ctx);
|
|
complete_macro_in_item_position::complete_macro_in_item_position(&mut acc, &ctx);
|
|
complete_trait_impl::complete_trait_impl(&mut acc, &ctx);
|
|
|
|
Some(acc)
|
|
}
|