Add consistency with foldMap law to UnorderedTraverseLaws #4803
+8
−2
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.
This adds that unorderedTraverse should be consistent with unorderedFoldMap, which seems intuitively obvious, but isn't checked.
Adding this law passes for both the current implementations of UnorderedTraverse (a typeclass I think very rarely used). However, note I just created: #4802 which argues that
UnorderedTraverse[Set]should be deprecated because it should be unlawful (although with the current laws it is not).