It seems that the RFC was updated to use the `Attributes` namespace. I
think this is a bad idea since we're reserving a generic namespace that we
haven't even "soft" reserved. Also, the loss of fallback to global
namespace is a turning point for me.
Generally, I think we should instead do
> On May 15, 2020, at 17:03, Arnold Daniels
> wrote:
>
> Hi all,
>
> I'd like to restart the discussion for the strict_opterators RFC (
> https://wiki.php.net/rfc/strict_operators).
I’m having trouble wrapping my head around this statement:
> To compare two numeric strings as numbers, they
Hi internals,
After 2 weeks, the vote for https://wiki.php.net/rfc/always_enable_json
("Always available JSON extension")
has been accepted, with 56 votes in favor and 0 votes against.
The proposal was to make it impossible to disable the JSON extension through
configuration or build options,
Am 16.05.2020 um 16:56 schrieb Max Semenik :
> On Sat, May 16, 2020 at 5:20 PM Mark Randall wrote:
>
>> IMHO we need to know what is happening with editions, as I think this
>> would be an ideal candidate for that rather than another declare
>
>
> On the other hand, a declare would allow a
On Wed, May 27, 2020 at 8:23 AM Alexandru Pătrănescu
wrote:
> In terms of what final does to a private method, as I understand, it will
> just be ignored everywhere? (except for constructor)
> I mean, final deny overriding but private methods cannot be overridden by
> design. We should have that
On Wed, May 27, 2020 at 2:08 AM Pedro Magalhães wrote:
> On Tue, May 26, 2020 at 3:46 PM Marco Pivetta wrote:
>
> > Considering that, as far as I know, only the constructor remains
> "special".
> >
>
> Leaving the special case only for constructors instead of all magic methods
> sounds better
