PHP 7: Fix negative bitshift error when no buckets are enabled #38
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.
If a slug exists in the database but no buckets are enabled, we get back
an empty string. The empty string gets coreced into 0, then we subtact
1 to do the bitshift, and we end up with the negative bitshift error. In
php 5.x this is a silent error where the value ends up being
int(-9223372036854775808), but in php 7.1 it's a fatal error.
With this change when we reduce the array, if $index is 0 we just return
the $mask we have accumulated so far. There's no need to shift the 0
$index so we avoid it by returning early.
Closes: #33
Below are some examples of what reduceToBitmask was returning:
Before:
Now: