Lines Matching defs:completion

626 /// A code completion consumer for the clang Sema that is responsible for
627 /// creating the completion suggestions when a user requests completion
635 /// The printing policy we use when printing declarations for our completion
640 /// This also returns true for numbers because for completion we usually
653 /// the completion of the cmd line. 'unrelated' means here that the token
654 /// is not interested for the lldb completion API result.
660 // the current completion logic.
683 /// Attemps to merge the given completion from the given position into the
684 /// existing command. Returns the completion string that can be returned to
685 /// the lldb completion API.
687 StringRef completion) {
689 // We rewrite the last token with the completion, so let's drop that
693 // would otherwise be added to the completion that already has the
694 // completion.
696 return existing_command.str() + completion.str();
726 /// Deregisters and destroys this code-completion consumer.
729 /// \name Code-completion filtering
747 // CodeCompletionResult has been enhanced with more kinds of completion
749 assert(false && "Unknown completion result type?");
752 // completion suggestion with the existing code.
756 /// \name Code-completion callbacks
757 /// Process the finalized code-completion results.
776 // Handle the different completion kinds that come from the Sema.
830 /// \param S the semantic-analyzer object for which code-completion is being
857 // class uses to provide completion suggestions.
867 // Start parsing the expression with our custom code completion consumer.
893 // Clang wants to do completion on a real file known by Clang's file manager,
945 // If we want to parse for code completion, we need to attach our code
946 // completion consumer to the Sema and specify a completion position.
948 // completion suggestions.
952 // Lines and columns start at 1 in Clang, but code completion positions are