It previously an easy way to concurrently access a mutable vfs, which
is a recipe for disaster.
Details
Details
Diff Detail
Diff Detail
- Repository
- rCTE Clang Tools Extra
Event Timeline
clangd/TUScheduler.h | ||
---|---|---|
81–82 | I think this is the right place to describe the way FS interaction works (which implies why we don't propagate vfs): /// The preamble may be stale, generated from an older version of the file. /// Reading from locations in the preamble may cause the files to be re-read. /// This gives callers two options: /// - validate that the preamble is still valid, and only use it in this case /// - accept that preamble contents may be outdated, and try to avoid reading source code from headers. |
I think this is the right place to describe the way FS interaction works (which implies why we don't propagate vfs):