Details
Details
- Reviewers
sammccall - Commits
- rG1c0d0085bcaa: [clangd] Get rid of arg adjusters in CommandMangler
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
This raises the question "is it safe to move functionality from CommandMangler to buildCompilerInvocation for convenience, are they always called on the same codepaths?"
I think from our brief investigation the answer is yes, but:
- this expectation should probably be documented on CommandMangler and/or buildCompilerInvocation
- *neither* of them are called when background indexing, which should probably be a fixme on the static indexer
clang-tools-extra/clangd/CompileCommands.cpp | ||
---|---|---|
226 | oops, might have left this comment on the wrong patch use range insert to save shuffling the tail over and over and std::make_move_iterator() to avoid copies? |
Comment Actions
Use move_iterator instead of inserting in a loop.
clang-tools-extra/clangd/CompileCommands.cpp | ||
---|---|---|
226 | yeah the main reason this is a loop is because I didn't know about make_move_iterator, switching to a range insert instead, thanks! |
oops, might have left this comment on the wrong patch
use range insert to save shuffling the tail over and over and std::make_move_iterator() to avoid copies?