clang-tools 19.0.0git
Namespaces | Classes | Typedefs | Functions
llvm Namespace Reference

Some operations such as code completion produce a set of candidates. More...


namespace  vfs
namespace  yaml


struct  DenseMapInfo< clang::clangd::Config::ExternalIndexSpec >
struct  DenseMapInfo< clang::clangd::dex::Token >
struct  DenseMapInfo< clang::clangd::dex::Trigram >
struct  DenseMapInfo< clang::clangd::IncludeStructure::HeaderID >
struct  DenseMapInfo< clang::clangd::Range >
struct  DenseMapInfo< clang::clangd::RefSlab::Builder::Entry >
struct  DenseMapInfo< clang::clangd::SymbolID >
struct  DenseMapInfo< clang::tidy::cppcoreguidelines::SpecialMemberFunctionsCheck::ClassDefId >
 Specialization of DenseMapInfo to allow ClassDefId objects in DenseMaps FIXME: Move this to the corresponding cpp file as is done for clang-tidy/readability/IdentifierNamingCheck.cpp. More...
struct  DenseMapInfo< clang::tidy::RenamerClangTidyCheck::NamingCheckId >
 Specialization of DenseMapInfo to allow NamingCheckId objects in DenseMaps. More...
struct  DenseMapInfo< DriverArgs >
struct  format_provider< clang::clangd::Position >
class  SmallVectorImpl


using DriverArgs = clang::clangd::DriverArgs


int get_physical_cores ()

Detailed Description

Some operations such as code completion produce a set of candidates.

Usually the user can choose between them, but we should put the best options at the top (they're easier to select, and more likely to be seen).

This file defines building blocks for ranking candidates. It's used by the features directly and also in the implementation of indexes, as indexes also need to heuristically limit their results.

The facilities here are:

Typedef Documentation

◆ DriverArgs

using llvm::DriverArgs = typedef clang::clangd::DriverArgs

Definition at line 217 of file SystemIncludeExtractor.cpp.

Function Documentation

◆ get_physical_cores()

int llvm::get_physical_cores ( )