Skip to content
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

analyze: track reasons why functions are not rewritten #1072

Merged
merged 10 commits into from
Apr 15, 2024

Conversation

spernsteiner
Copy link
Collaborator

This branch replaces most of the existing fns_failed/fns_fixed machinery with a new strategy for marking items with a "don't rewrite" flag. This makes it easier to integrate new, stricter checks for unsupported code patterns, with the goal of reducing compile errors in the rewritten code. Some of these checks are also implemented in this branch, such as a check for complex (and currently unsupported) Cell rewrites.

When an item is marked as don't-rewrite, we also record a reason flag. This is helpful for debugging, and will also make it easy in the future to disable specific checks (by ignoring the corresponding reason flag) for debugging/testing purposes or by user request.

@spernsteiner
Copy link
Collaborator Author

@fw-immunant @ahomescu Can one of you take a look at this? #1073 is approved but can't be merged yet because it's based on this PR (and would be nontrivial to rebase off of it)

@fw-immunant
Copy link
Contributor

I'll review today, I was sick most of the week.

@spernsteiner spernsteiner merged commit ff1fa02 into master Apr 15, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants