Fix multiple enumeration of collection in CollectionAssertions.Equal/NotEqual#438
Merged
dennisdoomen merged 2 commits intofluentassertions:masterfrom Jul 8, 2016
Merged
Conversation
of collection for CollectionAssertions.Equal/NotEqual
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
2 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.
Fixes #437
Equal: The solution is to materialize the subject before checking that it has the correct count and content. It might be an issue if the subject is a very large collection, butNotEqual(and probably others) already does it anyway...NotEqual: use the (already created) materialized copy of the subject to generate the assertion failure messageI only checked
EqualandNotEqual, but there might be other methods with the same issue.