Use InvalidScalarArgument only when we can be sure PHP attempts coercion #7188
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.
This is an alternative to #7181
It narrows the occasions where
InvalidScalarArgument
is emitted to only the places where we're sure that PHP will attempt to coerce one scalar type to another. This matches the original intent ofInvalidScalarArgument
— a lesser issue thanInvalidArgument
, for when the PHP runtime may not care.