Fix warnings under PHP 8.4 #1
Open
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
|
I'm also trying to contribute this upstream, but there's been no activity I can see since Feb 2022 so I don't realistically expect the PR to be accepted. I'll likely use this version as an alternate until/unless the changes land upstream. |
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.
8.4 starts issuing warnings about implicit nullable parameters, e.g.
int $foo = nullshould be?int $foo = null. This change corrects the signatures for compatibility.This also relatedly blocks versions of PHP with a regression in GMP, demonstrated at https://3v4l.org/lnhXp