This allows for providing completion results for include directive
file paths by searching the set of include directories for the current
file.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
mlir/lib/Tools/PDLL/Parser/Parser.cpp | ||
---|---|---|
685 | Is string sufficient differentiator? Don't we need to be inside include too? |
mlir/lib/Tools/PDLL/Parser/Parser.cpp | ||
---|---|---|
685 | Can you clarify what you mean here? If we hit a completion here inside of a string, that is for the include file. This method is only called from inside an include (Parser::parseInclude). |
mlir/lib/Tools/PDLL/Parser/Parser.cpp | ||
---|---|---|
685 | The token kind /// Token signifying a code completion location within a string. code_complete_string is more general, but I missed this part was only inside parseInclude. |
Is string sufficient differentiator? Don't we need to be inside include too?