Hello internals,
Following the discussion that started at
https://externals.io/message/128226#128456 I wrote this RFC to formalize
our consensus on the topic.
TL;DR, this is about converting the deprecation of __sleep and __wakeup to
a documentation-based soft deprecation:
https://wiki.php.net/rf
On Fri, Sep 5, 2025, at 22:01, Rowan Tommins [IMSoP] wrote:
> On 4 September 2025 15:50:08 BST, Rob Landers wrote:
> >I think this is a fair observation and a fair question; but I think it is
> >important not to have "magic". The power-of-two rule is to make it possible
> >to work back how $en
On 4 September 2025 15:50:08 BST, Rob Landers wrote:
>I think this is a fair observation and a fair question; but I think it is
>important not to have "magic". The power-of-two rule is to make it possible to
>work back how $enum->value === 15 (0x) even if you are completely new to
>the lang
Hi
Am 2025-09-04 20:17, schrieb Rob Landers:
Specifically “Other RFCs” (i.e. RFCs that do not touch the language,
which is not actually defined) “might” (this probably should read
“may”)
use a “smaller timeframe” that “should be at least a week” (i.e. it
may
also be 2 hours). In other words,
Hi
Am 2025-09-04 00:14, schrieb Ilija Tovilo:
When making non-editorial / non-typographical changes to the normative
section of the RFC text (i.e. to the actual proposal, excluding future
scope, rejected features and references) the discussion period MUST be
extended.
It should also be accep
