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

Fix crash on static send mutation #1108

Merged
merged 1 commit into from
Nov 16, 2020
Merged

Fix crash on static send mutation #1108

merged 1 commit into from
Nov 16, 2020

Conversation

mbj
Copy link
Owner

@mbj mbj commented Nov 16, 2020

No description provided.

@mbj mbj requested a review from dgollahon November 16, 2020 12:54
@mbj mbj self-assigned this Nov 16, 2020
@mbj mbj merged commit 76dc84f into master Nov 16, 2020
@mbj mbj deleted the fix/static-send branch November 16, 2020 13:03
@dgollahon
Copy link
Collaborator

Nice catch. I think I must have introduced that one.

@mbj
Copy link
Owner Author

mbj commented Nov 16, 2020

Yeah, but I reviewed it. So no blame assigned.

BTW: I think we need #1105 to handle these more gracefully, mutants AST is "to wide" to assume a dynlang can ever be correctly generate mutations in all cases. With types this would not happen.

@dgollahon
Copy link
Collaborator

We could probably do some automated testing of removing arguments from sends, etc. in the meta and making sure they don't crash. I suspect there are more cases like this generally.

Yeah, we very well might. My only concern about #1105 is that it will probably make it hard to receive bug reports since most users won't notice failures. That's still probably worth it, but a little unfortunate.

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