Nathan Ridge

Results 83 issues of Nathan Ridge

Spinning this out from #643 where it was originally requested. After making that change to use a dropdown to switch between using a background color for inactive regions and using...

enhancement

YAML 1.1 accepts both, but YAML 1.2 only accepts true/false. Our config parser uses YAML 1.1, but some popular validator tools (like RedHat's vscode-yaml) default to validating against YAML 1.2....

Especially now that we support both incoming and outgoing calls, it would be nice to illustrate such support with some screenshots in the [Navigation](https://clangd.llvm.org/features#navigation) section.

It would be nice to have some documentation geared towards clangd contributors. I know we have some info at https://github.com/llvm/llvm-project/tree/main/clang-tools-extra/clangd, but I don't think that's as discoverable as a page...

The preamble optimization often comes up in discussions about clangd's design, or when users run into constraints / bugs caused by it. It would be helpful to have a page...

In the following code example: ```c++ template void foo(T); template void foo(T, T); template void bar(T t) { foo(t); } ``` go-to-definition on `foo` in `foo(t)` offers both overloads as...

A common mistake users make in `.clangd` files is: ```yaml CompileFlags: Add: -I path ``` The mistake is that `-I path` is treated as a single argument, as if it...

enhancement

Our [release packages](https://github.com/clangd/clangd/releases) ship with a set of built-in headers (located in `lib/clang//include` in the package) which clangd uses regardless of the compiler that appears in the compiler commands (unless,...

Using the [Release checklist](https://github.com/clangd/clangd/wiki/Release-checklist) from the wiki as a template: ## Once the release branch is created - [x] https://github.com/llvm/llvm-project/pull/127358 - [x] https://github.com/llvm/clangd-www/pull/122 - [x] https://github.com/SchemaStore/schemastore/issues/4459 - [x] Document any...

In a case like the following: ```c++ template class A {}; template class B {}; template class C { void overload(A); void overload(B); void foo() { A a; overload(a); }...