Skip to content

Conversation

@rizwan3d
Copy link

@rizwan3d rizwan3d commented Dec 4, 2025

Implements proposal from #20632

rizwan3d and others added 3 commits December 4, 2025 19:25
@rizwan3d rizwan3d requested a review from mvorisek December 4, 2025 15:52
Copy link
Member

@iluuu1994 iluuu1994 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please also see my comment in #20632 (comment).

@rizwan3d rizwan3d requested a review from iluuu1994 December 4, 2025 19:24
@iluuu1994
Copy link
Member

I don't know if the code churn is worth it. @Girgias Opinions?

@@ -0,0 +1,35 @@
--TEST--
Error message for non-numaric strings in arithmetic contexts
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Error message for non-numaric strings in arithmetic contexts
Error message for non-numeric strings in arithmetic contexts

Copy link
Member

@Girgias Girgias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a lot of code churn and I don't even think the implementation is correct vis a vis strict_types.

I'd prefer a discussion on the mailing list, I can understand the rationale somewhat, but an empty string is non-numeric so this seems redundant?

And I'd be more inclined to do this just for binary ops, rather than all type checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants