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.

Sign up for GitHub

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

Jump to bottom

Investigate ways to avoid NOT VIABLE #109

Open

k3rn31 opened this issue Aug 6, 2022 · 0 comments

Labels

Member

k3rn31 commented Aug 6, 2022 •

edited

Loading

NOT VIABLE mutant status are usually compile errors. Can we detect them before actually trying the test?

Note: we don't want to rewrite the Go compiler static analyser.

k3rn31 added the c/enhancement label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment