-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What about using Clangd to reject mutations that would not compile #27
Comments
What is your exact proposal? |
The proposal is to start clangd as a part of the "Generate patches" run and use LSP to syntactically validate the patches before adding them to the database. I think that Clangd should be able to syntactically validate the patches much quicker than compiler would, as I think that Clangd does not need to reparse the whole document if only one line changed. This would save hours of time as there is no point in trying to compile patches that are obviously syntactically invalid, e.g. a patch
should not even get to the compilation stage, IMO... |
Resp. to be super exact: Mutate_cpp would listen to Clangd LSP messages such as
either during execution of the queue or during generation of the patchsets. It should be relatively easy to implement I guess. |
The point is that Clangd can probably detect errors much quicker than compiler itself as it uses indexing, and it does not need to reparse the whole file after just a single line was changes. Only the mutations that passed Clangd syntactic check would be compiled.
The text was updated successfully, but these errors were encountered: