def Lean.Server.Completion.findCompletionInfosAt (fileMap : FileMap) (hoverPos : String.Pos) (cmdStx : Syntax) (infoTree : Elab.InfoTree) : Array ContextualizedCompletionInfo × Bool

Equations

• One or more equations did not get rendered due to their size.

def Lean.Server.Completion.findPrioritizedCompletionPartitionsAt (fileMap : FileMap) (hoverPos : String.Pos) (cmdStx : Syntax) (infoTree : Elab.InfoTree) : Array (Array (ContextualizedCompletionInfo × Nat)) × Bool

Finds all CompletionInfos (both from the InfoTree and synthetic ones), prioritizes them, arranges them in partitions of CompletionInfos with the same priority and sorts these partitions so that CompletionInfos with the highest priority come first. The returned CompletionInfos are also tagged with their index in findCompletionInfosAt so that when resolving a CompletionItem, we can reconstruct which CompletionInfo it was created from.

In general, the InfoTree may contain multiple different CompletionInfos covering hoverPos, and so we need to decide which of these CompletionInfos we want to use to show completions to the user. We choose priorities by the following rules:

• Synthetic completions have the lowest priority since they are only intended as a backup.
• Non-identifier completions have the highest priority since they tend to be much more helpful than identifier completions when available since there are typically way too many of the latter.
• Within the three groups [non-id completions, id completions, synthetic completions], CompletionInfos with a smaller range are considered to be better.

Equations

• One or more equations did not get rendered due to their size.