C++: Don't generate IR for functions with bad ASTs #517
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many of the IR sanity check failures I've hit when running on real-world snapshots are due to the original ASTs being ill-formed in one way or another. This PR provides a filtering mechanism to avoid generating IR for functions that match an
isInvalidFunction
predicate, and then implements that predicate to filter out the issues that I already know about. I'll open an individual extractor bug for each of these.See individual commit messages for more detail.