> On Feb 23, 2020, at 2:00 AM, Mike Schinkel wrote:
> On Feb 22, 2020, at 5:56 AM, Rowan Tommins wrote:
>> One of the reasons it is confusing is because developers are currently
>> required to use the ampersand in one place and not the other. Making
>> it always used removes said confusion as
> The original motivation was, IIRC, to initialize class constants with an
> expression.
> Following KISS, I feel we should constrain our efforts to that scope, and
> that's how I voted:
> "Yes" on class constants and static members, "No" on everything else.
I'd also personally found the `static
jan.h.boeh...@gmx.de wrote:
based on the discussions here (https://externals.io/message/108300)
and here (https://github.com/php/php-src/pull/5156), I have created a
proper RFC for userspace operator overloading:
https://wiki.php.net/rfc/userspace_operator_overloading
The main differences to my
> On Feb 20, 2020, at 18:42, Mike Schinkel wrote:
>
>> On Feb 20, 2020, at 10:26 AM, Paul M. Jones wrote:
>>
>> One of the "open questions" on this RFC is: are the class names
>> ServerRequest, ServerResponse, and ServerResponseSender "good enough" for
>> our purposes, or are there names t
Hi all,
Off-list discussion with some vendors and consumers indicates that adoption and
migration might be eased by the following changes to ServerResponseInterface:
- Add the following methods:
- `getHeader(string $label) : ?string`
- `hasHeader(string $label) : bool`
- `getCookie(
On 22 February 2020 06:50:46 GMT+00:00, Mike Schinkel
wrote:
>> On Feb 21, 2020, at 5:20 PM, Rowan Tommins
>wrote:
>> My instinctive reaction is still one of frustration that the pain of
>removing call-site ampersands was in vain, and I will now be asked to
>put most of them back in.
>
>That is
