Skip to content

Language Server Overview ​

clice provides a suite of C++ development tools built on LLVM/Clang. This section documents what clice does, feature by feature, and the clangd issues each feature answers.

Languages ​

clice serves C, C++, CUDA, HIP and OpenCL, and Objective-C and Objective-C++ for reading code: semantic tokens, hover, navigation and references, call and type hierarchies, the outline, folding, workspace symbols and clice query know their classes, protocols, categories, methods, properties and instance variables, completion writes a message's selector, and rename takes classes, protocols, categories and instance variables. Renaming a method or a property is not supported, nor are Clang header modules (-fmodules, @import): a file compiles without them, and clice says so once. Like every project, an Objective-C one needs a compilation database, which CMake's Makefile and Ninja generators write; neither Xcode nor CMake's Xcode generator does.

CUDA and HIP files compile their device side, as Clang runs that job first. OpenCL C and C++ for OpenCL (.cl, .clcpp) compile as Clang compiles them, builtins included; a file no compilation database lists takes a rule's default_command, such as clang -cl-std=CL3.0. The VS Code extension gives .hip a hip language and the OpenCL extensions an opencl one, which VS Code has none of; .cl is Common Lisp's extension too, which files.associations gives back.

Features ​

Language Server Protocol features available when using clice as an editor backend.

FeatureStatus
Code Completion55 supported
Hover72 supported
Signature Help21 supported1 partial2 unsupported
Code Navigation117 supported1 partial6 unsupported
Rename9 supported
Diagnostics12 supported1 partial
Code Action38 supported
Semantic Tokens61 supported
Inlay Hints40 supported
Document Links5 supported1 partial
Document Symbols29 supported
Folding Ranges24 supported
Selection Ranges14 supported
Formatting4 supported
C++20 Modules9 supported
Header Contexts6 supported
Compilation9 supported

Legend ​

Each feature counts the documented capabilities on its page at each status:

  • supported — the capability works; a snapshot pins the behavior
  • partial — some of it works; the snapshot pins what does
  • unsupported — a documented gap; the snapshot pins what clice does instead