Remove Operator.NONE - #63
Merged
Merged
Conversation
Collaborator
|
Currently, Operator.NONE is only referenced by the MMSFValidator in MUSCLE. We could merge this after the MUSCLE iteration PR (PR#378) is merged, since that PR removes the MMSFValidator. |
IrisvdWerf
approved these changes
Jul 21, 2026
LourensVeen
approved these changes
Aug 8, 2026
LourensVeen
left a comment
LourensVeen
left a comment
Contributor
There was a problem hiding this comment.
Should be good. And #378 is merged so this can now also go.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
As discussed over slack:
Operator.NONE was meant as a fallback mechanism for crazy scenarios. It doesn't fit in the formal framework and (to our knowledge) isn't used.