I recently ran into the issue that fortls did not jump to the correct definition in a large code base, as there existed several globals with the same name, but in different compilation units, so they were not actually compiled together. From using clangd for C and C++ I really liked the approach of parsing a compile_commands.json file to pass the actual compilation flags to the language server.
Describe the solution you'd like
I would like to add support for parsing compile_commands.json files in fortls to enable module disambiguation when multiple modules share the same name across different compilation units.
I intent to implement this using AI coding agents, as this is a substantial change and I am not familiar with this codebase. I did this locally, found that my changes had the effect I wanted and thought other people might like this feature as well. The PR is #504.
I recently ran into the issue that
fortlsdid not jump to the correct definition in a large code base, as there existed several globals with the same name, but in different compilation units, so they were not actually compiled together. From usingclangdfor C and C++ I really liked the approach of parsing acompile_commands.jsonfile to pass the actual compilation flags to the language server.Describe the solution you'd like
I would like to add support for parsing
compile_commands.jsonfiles infortlsto enable module disambiguation when multiple modules share the same name across different compilation units.I intent to implement this using AI coding agents, as this is a substantial change and I am not familiar with this codebase. I did this locally, found that my changes had the effect I wanted and thought other people might like this feature as well. The PR is #504.