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

Mutators don't need names #1379

Closed
wants to merge 1 commit into from
Closed

Conversation

addisoncrump
Copy link
Collaborator

The mutators don't need names

@domenukk
Copy link
Member

Could it be that, at some point, we might want to keep track of the names to know what mutator found a new testcase, or something?
I mean we can always bring it back by then, but ..

@addisoncrump
Copy link
Collaborator Author

If so, we should enforce Mutator: Named. As of now, we don't, which means that some mutators are incompatible with MutatorTuple (e.g., cannot put a scheduled mutator insight a mutator tuple)

@domenukk
Copy link
Member

We could enforce that? Is there ever a reason to have this guy unnamed?

domenukk added a commit that referenced this pull request Jul 31, 2023
domenukk added a commit that referenced this pull request Aug 1, 2023
* Mutators need names (alternative to #1379)

* Signature of MultiMutator shouldn't be the same as the normal mutator

* Named for python, remove mutator for multi_mutator

* fmt

* clippy edition warning

* clippy

* mac_count doc fix, return cleanup
@domenukk domenukk deleted the mutators-dont-need-names branch March 18, 2024 07:45
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.

None yet

2 participants