[5.6] Let Arr::wrap(null) return empty array #21745
Merged
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
|
The semantics of the word "wrap" indicate, to me, that I will get whatever value I pass in wrapped in an array. Sure, there's a special-case for arrays, and that annoys me, but I disagree on adding more of these special cases. Why shouldn't |
jmarcher
reviewed
Oct 19, 2017
| @@ -601,6 +601,10 @@ public static function where($array, callable $callback) | |||
| */ | |||
There was a problem hiding this comment.
Change comment: "If the given value is not an array, wrap it in one." is no longer true in this case.
|
@sisve I understand your thoughts. In the end, it's a design decision. But for me, it appears to be more useful like Ruby implemented it. |
|
I do like matching other ecosystems where possible. |
|
This also matches the array cast in PHP. |
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.
Change
Arr::wrapfunction to return an empty array when providing null as argument. This is the same way Ruby handles it and also more intuitive IMO