Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:109502
MIME-Version: 1.0
Date: Thu, 2 Apr 2020 10:14:26 +0200
Message-ID: <CAF+90c-=2RBpVHk2Ri3oeTTMkHN3VjKe4SNG8sXAoFB7vVimYA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000008da91305a24a641d"
Subject: [RFC] Stricter type-checks for arithmetic/bitwise operators
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000008da91305a24a641d
Content-Type: text/plain; charset="UTF-8"

Hi internals,

I would like to propose making the use of arithmetic/bitwise operators on
arrays, resources and (non-overloaded) objects a TypeError exception:

https://wiki.php.net/rfc/arithmetic_operator_type_checks

This is inspired by some of the recent discussions, in particular the
operator overloading RFC (where the fact that operations on non-overloaded
objects still succeed with just a notice was criticized) and the
increment/decrement RFC, which handles the array case of this proposal for
inc/dec only.

I think as-is, this RFC should be completely uncontroversial. However,
there is an open question on whether we want to make this slightly more
strict, in order to align the semantics with the rules for weak parameter
type checks for ints/floats.

If we do that, then this RFC could be a stepping stone towards making
"implicit" internal casts use the (weak) parameter type checking semantics
more generally, which I think would be a good idea. The current explicit
cast semantics we use everywhere are too forgiving for most circumstances
(e.g. an array is almost always not a reasonable input where an integer is
expected).

Regards,
Nikita

--0000000000008da91305a24a641d--