On 09.01.2022 at 14:15, Sebastian Bergmann wrote:
> Am 26.11.2021 um 10:06 schrieb Nikita Popov:
>> The RFC has been accepted with 52 votes in favor and 25 against.
>
> Has this been merged yet? Thanks!
Yes, it has been merged on Nov 26th, 2021[1]. FWIW, it's already
available on ev4l.org[2].
[
Am 26.11.2021 um 10:06 schrieb Nikita Popov:
The RFC has been accepted with 52 votes in favor and 25 against.
Has this been merged yet? Thanks!
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: https://www.php.net/unsub.php
On Wed, Dec 1, 2021 at 9:16 PM Sara Golemon wrote:
>
> On Tue, Nov 30, 2021 at 10:18 PM Brady Wetherington
> wrote:
>>
>> >>> …It's been merged to master, so you could stand up a build now and point
>> >>> to the many deprecation warnings you're expecting. I'm not saying send
>> >>> PRs to fi
On Tue, Nov 30, 2021 at 10:18 PM Brady Wetherington <
bwethering...@grokability.com> wrote:
> >>> …It's been merged to master, so you could stand up a build now and
> point to the many deprecation warnings you're expecting. I'm not saying
> send PRs to fix them all, just show real impact rather t
On Tue, Nov 30, 2021, at 10:17 PM, Brady Wetherington via internals wrote:
…It's been merged to master, so you could stand up a build now and point
to the many deprecation warnings you're expecting. I'm not saying send
PRs to fix them all, just show real impact rather than theoret
>>> …It's been merged to master, so you could stand up a build now and point to
>>> the many deprecation warnings you're expecting. I'm not saying send PRs to
>>> fix them all, just show real impact rather than theoretical guessing. …
>
>
> That’s a totally fair ask, and I’ll try and get that do
>
> …It's been merged to master, so you could stand up a build now and point
>> to the many deprecation warnings you're expecting. I'm not saying send PRs
>> to fix them all, just show real impact rather than theoretical guessing. …
>
>
That’s a totally fair ask, and I’ll try and get that done and
On Fri, Nov 26, 2021 at 12:16 AM Brady Wetherington via internals <
internals@lists.php.net> wrote:
> > > That's 1.5 million hours, which is 171 developer-years.
> >
> > If we're going to imagine numbers; there are 6 million PHP developers
> > in the world*. If on average they each lose just 1 hou
> > That's 1.5 million hours, which is 171 developer-years.
>
> If we're going to imagine numbers; there are 6 million PHP developers
> in the world*. If on average they each lose just 1 hour per year by
> making typos and accidentally creating a properties dynamically,
> that's 6 million hours, or
On Fri, 26 Nov 2021 at 00:55, Brady Wetherington via internals
wrote:
>
> That's 1.5 million hours, which is 171 developer-years.
If we're going to imagine numbers; there are 6 million PHP developers
in the world*. If on average they each lose just 1 hour per year by
making typos and accidentally
> This is a little bit overly dramatic. This isn't such a huge change that
> would affect 50% of existing projects. It's likely to affect a small number
> of projects in a very limited way.
> It's also not true that developers will slap #[AllowDynamicProperties] on
> every class. That would impl
Hi Brady,
This is a little bit overly dramatic. This isn't such a huge change that
would affect 50% of existing projects. It's likely to affect a small number
of projects in a very limited way.
It's also not true that developers will slap #[AllowDynamicProperties] on
every class. That would imply
12 matches
Mail list logo
