Details
- Reviewers
hokein - Commits
- rGdf537bef6393: Use pseudoparser-based folding ranges in ClangdServer.
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
as discussed offline i don't see much value in having an extra flag to choose between ast-based and pseudo-based implementation, as the pseudo-based one is a super-set of the ast-based implementation. hence it shouldn't be regressing change in any way, therefore i am in favor of just using the pseudo based implementation inside clangdserver at all times (this is already hidden behind a flag ATM).
independent of that, branch cut is next tuesday. so i'd rather not land it until the cut happens (existing implementation is also crashing, but it's the devil we know and it would be nice to not introduce new failures).
clang-tools-extra/clangd/ClangdServer.cpp | ||
---|---|---|
855 | i think choice of runQuick deserves a comment. something like We want to make sure folding ranges are always available for all the open files, hence prefer runQuick to not wait for operations on other files |
The change looks good to me.
as discussed offline i don't see much value in having an extra flag to choose between ast-based and pseudo-based implementation, as the pseudo-based one is a super-set of the ast-based implementation. hence it shouldn't be regressing change in any way, therefore i am in favor of just using the pseudo based implementation inside clangdserver at all times (this is already hidden behind a flag ATM).
+1
independent of that, branch cut is next tuesday. so i'd rather not land it until the cut happens (existing implementation is also crashing, but it's the devil we know and it would be nice to not introduce new failures).
What the main concern here? This feature is hidden under a flag which is off by default (and I don't think any user would turn it because the syntax-tree implementation is crashy), it should not affect any users, so it seems fine to land it even before the branch cut.
i think choice of runQuick deserves a comment. something like We want to make sure folding ranges are always available for all the open files, hence prefer runQuick to not wait for operations on other files