You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that the Eq instance should be just derived and current implementation should be exported as separate function. Besides, using allRotations is surely not the most optimal way of implementing the desired behavior. What if two CLists contain different sets of elements? Current implementation will check all the rotations, while it is possible to return False after finding the first element which is present in one of the given CLists but not in the other.
The text was updated successfully, but these errors were encountered:
As stated here,
Currently we have, e.g.
I think that the
Eq
instance should be just derived and current implementation should be exported as separate function. Besides, usingallRotations
is surely not the most optimal way of implementing the desired behavior. What if two CLists contain different sets of elements? Current implementation will check all the rotations, while it is possible to returnFalse
after finding the first element which is present in one of the givenCList
s but not in the other.The text was updated successfully, but these errors were encountered: