It's great that I can change the parser arguments in "Configure Language Support"! But when I give a wrong one, KDevelop doesn't tell me about that but parses the code wrongly. It would be better, if KDevelop mentions problems with the command line arguments that aren't accepted by the underlying libclang. Example: I wanted to use some C++17 features and since this is not selectable in the Profile dropdown, I added -std=c++17 to the arguments. But clang only accepts -std=c++1z for now instead, which means not even C++11/14 is parsed anymore.
+1. We should probably validate the command-line arguments & show hints in the config dialog. Marking as junior job.