Remove outdated documentation information from Set.to_a
#36
Conversation
This file contains 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
This information is no longer true since ruby 1.9, when hashes started having its elements iterated in order of their respective insertion. The methods `delete_if` and `keep if` in this same class even go on the length of ensure the *subclasses won't break the enumeration order*.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Just removing the note "The order of elements is uncertain." from the documentation.
This information is no longer true since ruby 1.9, when hashes started having its elements iterated in order of their respective insertion.
The methods
delete_ifandkeep ifin this same class even go on the length of ensure the subclasses won't break the enumeration order.