>
> Can I ask why you use late static binding while you don't want your
> constant value to be changed/overridden by child classes? IMHO, `self::FOO`
> is all you need.
>
Personally, I don't use late static binding with class constants since the
coding standard rule I previously referenced forbids
Hi Pierre,
Having type-inference wouldn't transparently fix some of these issues ?
>
> Let's consider a method such as foo($array) which returns a bool or a
> string, for example. And suddenly, the types get specified as foo(?array
> $array): bool|string.
>
PHP doesn't have such an advanced type
Hi internals,
I'm looking for someone to test the performance impact of a change to PHP.
Specifically the change affects how PHP does string concatenation, in
regards to the is_literal() RFC[1], where Joe Watkins has created an
initial patch[2].
This might not be the final version, I just want t
Le 20/04/2021 à 11:44, Máté Kocsis a écrit :
Hi Pierre,
PHP doesn't have such an advanced type inference capability: just consider
dynamic calls, or regular function invocations
where the return type information is not available.
Yes I know it doesn't have it, it was a subtle way of asking if one
> Yes I know it doesn't have it, it was a subtle way of asking if one day,
> the compiler may have inferences capabilities. I know it's not really
> possible until it continues loading code dynamically at runtime, but in
> some scenarios (such as preload, or inherited/implemented class type
> check
