Does this work well with C++17?

[33ILMX]

Just curious, if this would work with C++ 17 or only 20?
Would it be hard to adapt it?

Thanks for your help.

[walti1972]

Hi,

yes, it should work with C++17 projects as well.

The indexer is not tied to C++20 as a language requirement. It does not compile the project and it is not a full semantic analyzer; it builds a lightweight source-range index so an AI can locate symbols/files and then read the exact source ranges.

C++20 modules are supported as an additional feature, but they are not required. For example, we also tested it on a large Chromium checkout, which is a classic include-based codebase for this purpose and produced no C++20 module entries in the index. Module-related sections are simply empty or unused when the project does not use modules.

So adapting it for a normal C++17 project should usually not be hard. The main tuning points are project discovery settings, file extensions, excluded folders, and possible edge cases around heavy macros or unusual declaration patterns.

If you have a specific C++17 project shape in mind, I’d be happy to test it or look at a small example.