2017-05-16 17:38:59 +08:00
|
|
|
//===--- ClangdLSPServer.h - LSP server --------------------------*- C++-*-===//
|
|
|
|
//
|
|
|
|
// The LLVM Compiler Infrastructure
|
|
|
|
//
|
|
|
|
// This file is distributed under the University of Illinois Open Source
|
|
|
|
// License. See LICENSE.TXT for details.
|
|
|
|
//
|
|
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
|
|
|
|
#ifndef LLVM_CLANG_TOOLS_EXTRA_CLANGD_CLANGDLSPSERVER_H
|
|
|
|
#define LLVM_CLANG_TOOLS_EXTRA_CLANGD_CLANGDLSPSERVER_H
|
|
|
|
|
|
|
|
#include "ClangdServer.h"
|
2017-06-13 23:59:43 +08:00
|
|
|
#include "GlobalCompilationDatabase.h"
|
2017-05-16 17:38:59 +08:00
|
|
|
#include "Path.h"
|
|
|
|
#include "Protocol.h"
|
2017-09-30 18:08:52 +08:00
|
|
|
#include "ProtocolHandlers.h"
|
2017-05-16 17:38:59 +08:00
|
|
|
#include "clang/Tooling/Core/Replacement.h"
|
2017-07-19 23:43:35 +08:00
|
|
|
#include "llvm/ADT/Optional.h"
|
2017-05-16 17:38:59 +08:00
|
|
|
|
|
|
|
namespace clang {
|
|
|
|
namespace clangd {
|
|
|
|
|
|
|
|
class JSONOutput;
|
2018-01-10 22:44:34 +08:00
|
|
|
class SymbolIndex;
|
2017-05-16 17:38:59 +08:00
|
|
|
|
2017-05-16 22:40:30 +08:00
|
|
|
/// This class provides implementation of an LSP server, glueing the JSON
|
|
|
|
/// dispatch and ClangdServer together.
|
2017-09-30 18:08:52 +08:00
|
|
|
class ClangdLSPServer : private DiagnosticsConsumer, private ProtocolCallbacks {
|
2017-05-16 17:38:59 +08:00
|
|
|
public:
|
2017-10-02 23:13:20 +08:00
|
|
|
/// If \p CompileCommandsDir has a value, compile_commands.json will be
|
|
|
|
/// loaded only from \p CompileCommandsDir. Otherwise, clangd will look
|
|
|
|
/// for compile_commands.json in all parent directories of each file.
|
2017-08-14 16:45:47 +08:00
|
|
|
ClangdLSPServer(JSONOutput &Out, unsigned AsyncThreadsCount,
|
2017-11-24 00:58:22 +08:00
|
|
|
bool StorePreamblesInMemory,
|
|
|
|
const clangd::CodeCompleteOptions &CCOpts,
|
2017-10-02 23:13:20 +08:00
|
|
|
llvm::Optional<StringRef> ResourceDir,
|
2017-12-20 02:00:37 +08:00
|
|
|
llvm::Optional<Path> CompileCommandsDir,
|
2018-01-10 22:44:34 +08:00
|
|
|
bool BuildDynamicSymbolIndex,
|
|
|
|
SymbolIndex *StaticIdx = nullptr);
|
2017-05-16 17:38:59 +08:00
|
|
|
|
2017-05-16 22:40:30 +08:00
|
|
|
/// Run LSP server loop, receiving input for it from \p In. \p In must be
|
|
|
|
/// opened in binary mode. Output will be written using Out variable passed to
|
|
|
|
/// class constructor. This method must not be executed more than once for
|
|
|
|
/// each instance of ClangdLSPServer.
|
2017-10-25 16:45:41 +08:00
|
|
|
///
|
|
|
|
/// \return Wether we received a 'shutdown' request before an 'exit' request
|
2018-02-06 18:47:30 +08:00
|
|
|
bool run(std::istream &In,
|
|
|
|
JSONStreamStyle InputStyle = JSONStreamStyle::Standard);
|
2017-05-16 17:38:59 +08:00
|
|
|
|
2017-05-16 22:40:30 +08:00
|
|
|
private:
|
2017-09-30 18:08:52 +08:00
|
|
|
// Implement DiagnosticsConsumer.
|
|
|
|
virtual void
|
[clangd] Pass Context implicitly using TLS.
Summary:
Instead of passing Context explicitly around, we now have a thread-local
Context object `Context::current()` which is an implicit argument to
every function.
Most manipulation of this should use the WithContextValue helper, which
augments the current Context to add a single KV pair, and restores the
old context on destruction.
Advantages are:
- less boilerplate in functions that just propagate contexts
- reading most code doesn't require understanding context at all, and
using context as values in fewer places still
- fewer options to pass the "wrong" context when it changes within a
scope (e.g. when using Span)
- contexts pass through interfaces we can't modify, such as VFS
- propagating contexts across threads was slightly tricky (e.g.
copy vs move, no move-init in lambdas), and is now encapsulated in
the threadpool
Disadvantages are all the usual TLS stuff - hidden magic, and
potential for higher memory usage on threads that don't use the
context. (In practice, it's just one pointer)
Reviewers: ilya-biryukov
Subscribers: klimek, jkorous-apple, ioeric, cfe-commits
Differential Revision: https://reviews.llvm.org/D42517
llvm-svn: 323872
2018-01-31 21:40:48 +08:00
|
|
|
onDiagnosticsReady(PathRef File,
|
2017-09-30 18:08:52 +08:00
|
|
|
Tagged<std::vector<DiagWithFixIts>> Diagnostics) override;
|
|
|
|
|
|
|
|
// Implement ProtocolCallbacks.
|
[clangd] Pass Context implicitly using TLS.
Summary:
Instead of passing Context explicitly around, we now have a thread-local
Context object `Context::current()` which is an implicit argument to
every function.
Most manipulation of this should use the WithContextValue helper, which
augments the current Context to add a single KV pair, and restores the
old context on destruction.
Advantages are:
- less boilerplate in functions that just propagate contexts
- reading most code doesn't require understanding context at all, and
using context as values in fewer places still
- fewer options to pass the "wrong" context when it changes within a
scope (e.g. when using Span)
- contexts pass through interfaces we can't modify, such as VFS
- propagating contexts across threads was slightly tricky (e.g.
copy vs move, no move-init in lambdas), and is now encapsulated in
the threadpool
Disadvantages are all the usual TLS stuff - hidden magic, and
potential for higher memory usage on threads that don't use the
context. (In practice, it's just one pointer)
Reviewers: ilya-biryukov
Subscribers: klimek, jkorous-apple, ioeric, cfe-commits
Differential Revision: https://reviews.llvm.org/D42517
llvm-svn: 323872
2018-01-31 21:40:48 +08:00
|
|
|
void onInitialize(InitializeParams &Params) override;
|
|
|
|
void onShutdown(ShutdownParams &Params) override;
|
|
|
|
void onExit(ExitParams &Params) override;
|
|
|
|
void onDocumentDidOpen(DidOpenTextDocumentParams &Params) override;
|
|
|
|
void onDocumentDidChange(DidChangeTextDocumentParams &Params) override;
|
|
|
|
void onDocumentDidClose(DidCloseTextDocumentParams &Params) override;
|
2017-10-12 21:29:58 +08:00
|
|
|
void
|
[clangd] Pass Context implicitly using TLS.
Summary:
Instead of passing Context explicitly around, we now have a thread-local
Context object `Context::current()` which is an implicit argument to
every function.
Most manipulation of this should use the WithContextValue helper, which
augments the current Context to add a single KV pair, and restores the
old context on destruction.
Advantages are:
- less boilerplate in functions that just propagate contexts
- reading most code doesn't require understanding context at all, and
using context as values in fewer places still
- fewer options to pass the "wrong" context when it changes within a
scope (e.g. when using Span)
- contexts pass through interfaces we can't modify, such as VFS
- propagating contexts across threads was slightly tricky (e.g.
copy vs move, no move-init in lambdas), and is now encapsulated in
the threadpool
Disadvantages are all the usual TLS stuff - hidden magic, and
potential for higher memory usage on threads that don't use the
context. (In practice, it's just one pointer)
Reviewers: ilya-biryukov
Subscribers: klimek, jkorous-apple, ioeric, cfe-commits
Differential Revision: https://reviews.llvm.org/D42517
llvm-svn: 323872
2018-01-31 21:40:48 +08:00
|
|
|
onDocumentOnTypeFormatting(DocumentOnTypeFormattingParams &Params) override;
|
2017-10-12 21:29:58 +08:00
|
|
|
void
|
[clangd] Pass Context implicitly using TLS.
Summary:
Instead of passing Context explicitly around, we now have a thread-local
Context object `Context::current()` which is an implicit argument to
every function.
Most manipulation of this should use the WithContextValue helper, which
augments the current Context to add a single KV pair, and restores the
old context on destruction.
Advantages are:
- less boilerplate in functions that just propagate contexts
- reading most code doesn't require understanding context at all, and
using context as values in fewer places still
- fewer options to pass the "wrong" context when it changes within a
scope (e.g. when using Span)
- contexts pass through interfaces we can't modify, such as VFS
- propagating contexts across threads was slightly tricky (e.g.
copy vs move, no move-init in lambdas), and is now encapsulated in
the threadpool
Disadvantages are all the usual TLS stuff - hidden magic, and
potential for higher memory usage on threads that don't use the
context. (In practice, it's just one pointer)
Reviewers: ilya-biryukov
Subscribers: klimek, jkorous-apple, ioeric, cfe-commits
Differential Revision: https://reviews.llvm.org/D42517
llvm-svn: 323872
2018-01-31 21:40:48 +08:00
|
|
|
onDocumentRangeFormatting(DocumentRangeFormattingParams &Params) override;
|
|
|
|
void onDocumentFormatting(DocumentFormattingParams &Params) override;
|
|
|
|
void onCodeAction(CodeActionParams &Params) override;
|
|
|
|
void onCompletion(TextDocumentPositionParams &Params) override;
|
|
|
|
void onSignatureHelp(TextDocumentPositionParams &Params) override;
|
|
|
|
void onGoToDefinition(TextDocumentPositionParams &Params) override;
|
|
|
|
void onSwitchSourceHeader(TextDocumentIdentifier &Params) override;
|
|
|
|
void onDocumentHighlight(TextDocumentPositionParams &Params) override;
|
|
|
|
void onFileEvent(DidChangeWatchedFilesParams &Params) override;
|
|
|
|
void onCommand(ExecuteCommandParams &Params) override;
|
|
|
|
void onRename(RenameParams &Parames) override;
|
2017-05-16 17:38:59 +08:00
|
|
|
|
[clangd] Emit ranges for clangd diagnostics, and fix off-by-one positions
Summary:
- when the diagnostic has an explicit range, we prefer that
- if the diagnostic has a fixit, its RemoveRange is our next choice
- otherwise we try to expand the diagnostic location into a whole token.
(inspired by VSCode, which does this client-side when given an empty range)
- if all else fails, we return the zero-width range as now.
(clients react in different ways to this, highlighting a token or a char)
- this includes the off-by-one fix from D40860, and borrows heavily from it
Reviewers: rwols, hokein
Subscribers: klimek, ilya-biryukov, cfe-commits
Differential Revision: https://reviews.llvm.org/D41118
llvm-svn: 320555
2017-12-13 16:48:42 +08:00
|
|
|
std::vector<TextEdit> getFixIts(StringRef File, const clangd::Diagnostic &D);
|
2017-05-16 17:38:59 +08:00
|
|
|
|
|
|
|
JSONOutput &Out;
|
2017-05-16 22:40:30 +08:00
|
|
|
/// Used to indicate that the 'shutdown' request was received from the
|
|
|
|
/// Language Server client.
|
2017-10-25 16:45:41 +08:00
|
|
|
bool ShutdownRequestReceived = false;
|
|
|
|
|
|
|
|
/// Used to indicate that the 'exit' notification was received from the
|
|
|
|
/// Language Server client.
|
2017-05-16 22:40:30 +08:00
|
|
|
/// It's used to break out of the LSP parsing loop.
|
|
|
|
bool IsDone = false;
|
2017-05-16 17:38:59 +08:00
|
|
|
|
|
|
|
std::mutex FixItsMutex;
|
2017-12-20 04:52:56 +08:00
|
|
|
typedef std::map<clangd::Diagnostic, std::vector<TextEdit>,
|
|
|
|
LSPDiagnosticCompare>
|
2017-05-16 17:38:59 +08:00
|
|
|
DiagnosticToReplacementMap;
|
|
|
|
/// Caches FixIts per file and diagnostics
|
|
|
|
llvm::StringMap<DiagnosticToReplacementMap> FixItsMap;
|
2017-06-13 23:59:43 +08:00
|
|
|
|
|
|
|
// Various ClangdServer parameters go here. It's important they're created
|
|
|
|
// before ClangdServer.
|
|
|
|
DirectoryBasedGlobalCompilationDatabase CDB;
|
|
|
|
RealFileSystemProvider FSProvider;
|
2017-12-05 18:42:57 +08:00
|
|
|
/// Options used for code completion
|
|
|
|
clangd::CodeCompleteOptions CCOpts;
|
2017-05-16 17:38:59 +08:00
|
|
|
// Server must be the last member of the class to allow its destructor to exit
|
|
|
|
// the worker thread that may otherwise run an async callback on partially
|
|
|
|
// destructed instance of ClangdLSPServer.
|
|
|
|
ClangdServer Server;
|
|
|
|
};
|
|
|
|
|
|
|
|
} // namespace clangd
|
|
|
|
} // namespace clang
|
|
|
|
|
|
|
|
#endif
|