clangd's database is the one CMake Tools copies from the selected preset,
as in libavr, rather than one chip's tree. .gitattributes drops two Studio
patterns nothing here matches, .clangd is ASCII, and the comments in it,
check.sh and .gitattributes state the reason without the account of how it
was found.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The three files libavr's consumers carry: .vscode/settings.json names the
atmega328p-generated database and passes --query-driver, .clangd holds the
stand-ins clang needs for GCC's AVR dialect -- and no database, because this
driver is made to be vendored and the file travels with it -- and
extensions.json names the two extensions. The libavr pin advances to the
editor-audit fixes, without which every TU inherits device.hpp's
alias-shadowing errors. The preset builds green from the pin and clangd
reports zero errors on the example TU.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
BlackMarkandClaude Opus 5.5