#include <Protocol.h>

Public Member Functions
	URIForFile ()=default
llvm::StringRef	file () const
	Retrieves absolute path to the file.
	operator bool () const
std::string	uri () const

Static Public Member Functions
static URIForFile	canonicalize (llvm::StringRef AbsPath, llvm::StringRef TUPath)
static llvm::Expected< URIForFile >	fromURI (const URI &U, llvm::StringRef HintPath)

Friends
bool	operator== (const URIForFile &LHS, const URIForFile &RHS)
bool	operator!= (const URIForFile &LHS, const URIForFile &RHS)
bool	operator< (const URIForFile &LHS, const URIForFile &RHS)

Detailed Description

Definition at line 57 of file lspserver/include/lspserver/Protocol.h.

Constructor & Destructor Documentation

◆ URIForFile()

lspserver::URIForFile::URIForFile ( )

default

References URIForFile().

Referenced by canonicalize(), fromURI(), operator!=, operator<, operator==, and URIForFile().

Member Function Documentation

◆ canonicalize()

URIForFile lspserver::URIForFile::canonicalize	(	llvm::StringRef	AbsPath,
		llvm::StringRef	TUPath )

static

Canonicalizes AbsPath via URI.

File paths in URIForFile can come from index or local AST. Path from index goes through URI transformation, and the final path is resolved by URI scheme and could potentially be different from the original path. Hence, we do the same transformation for all paths.

Files can be referred to by several paths (e.g. in the presence of links). Which one we prefer may depend on where we're coming from. TUPath is a hint, and should usually be the main entrypoint file we're processing.

Definition at line 43 of file lspserver/src/Protocol.cpp.

References lspserver::elog(), lspserver::URI::resolvePath(), and URIForFile().

Referenced by nixd::addExtractToFileAction().