-
Notifications
You must be signed in to change notification settings - Fork 8.1k
Add array_search_range() function #23325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sepehrphpr
wants to merge
1
commit into
php:master
Choose a base branch
from
sepehrphpr:array_search_range
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+109
−0
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,35 @@ | ||
| --TEST-- | ||
| array_search_range() function - basic test | ||
| --FILE-- | ||
| <?php | ||
| $array = ['a' => 1, 'b' => 2, 'c' => 3, 'd' => 2, 'e' => 1]; | ||
|
|
||
| // Search from beginning | ||
| var_dump(array_search_range(2, $array)); | ||
|
|
||
| // Search with offset | ||
| var_dump(array_search_range(2, $array, 2)); | ||
|
|
||
| // Search with offset and length | ||
| var_dump(array_search_range(2, $array, 0, 2)); | ||
|
|
||
| // Search with strict comparison | ||
| var_dump(array_search_range('2', $array, 0, null, true)); | ||
|
|
||
| // Search with negative offset | ||
| var_dump(array_search_range(1, $array, -2)); | ||
|
|
||
| // Search with length | ||
| var_dump(array_search_range(3, $array, 0, 3)); | ||
|
|
||
| // Not found | ||
| var_dump(array_search_range(10, $array)); | ||
| ?> | ||
| --EXPECT-- | ||
| string(1) "b" | ||
| string(1) "d" | ||
| string(1) "b" | ||
| bool(false) | ||
| string(1) "e" | ||
| string(1) "c" | ||
| bool(false) |
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this is still going to iterate the whole array, and only the comparison is optimised. That's still going to be inefficient for very large arrays.
Completely ignoring the elements after the offset is trivial:
But if you look at the implementation of
array_slice, it has extra optimisations for finding the start offset - some arrays are laid out sequentially in memory, so the memory address can be calculated without iterating.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for pointing that out — that’s a really good catch, and I can see how array_slice’s handling of packed arrays is the right way to think about the offset lookup.
You’re absolutely right that the simpler range check still walks the whole array, and skipping past the offset (or breaking out once we pass offset + max_count) is the correct optimisation. I’ll apply that.
Appreciate you taking the time to review this