Re: [PHP-DEV] [RFC] [DISCUSSION] Immutable/final/readonly properties

2020-03-12 Thread Larry Garfield
On Thu, Mar 12, 2020, at 8:57 AM, Máté Kocsis wrote: > As you might noticed, I've not opened the vote yet. Partly because I was > improving > my implementation as well as the RFC itself (added some words about the > inheritance > implications), but the main reason is that a question arise in the >

Re: [PHP-DEV] RFC: Server-Side Request and Response Objects (v2)

2020-03-12 Thread Paul M. Jones
Hi all, > On Mar 11, 2020, at 11:36, Paul M. Jones wrote: > > Conversation on this RFC seems to have diminished. As far as I know, I have > answered all criticisms/concerns/complaints one way or another. FWIW, I have updated the Q&A points based on new discussion over the past day or so. The

Re: [PHP-DEV] [RFC] [DISCUSSION] Immutable/final/readonly properties

2020-03-12 Thread Máté Kocsis
As you might noticed, I've not opened the vote yet. Partly because I was improving my implementation as well as the RFC itself (added some words about the inheritance implications), but the main reason is that a question arise in the meanwhile. Namely, "write-once" properties could in principle su

Re: [PHP-DEV] [VOTE] Object-based token_get_all() alternative

2020-03-12 Thread Côme Chilliet
Le mercredi 11 mars 2020, 10:59:19 CET Larry Garfield a écrit : > I forget who it was but someone on the list a while back offered a heuristic > of "__toString should be used iff there is one and only one logical string > representation of a value, because the value is conceptually just a string

Re: [PHP-DEV] Re: [RFC] Userspace operator overloading

2020-03-12 Thread Rowan Tommins
On Thu, 12 Mar 2020 at 08:31, Jan Böhmer wrote: > On 11.03.2020 at 10:50, Christoph M. Becker wrote: > > On 11.03.2020 at 10:22, Nikita Popov wrote: > >> Does anyone else have thoughts on the ability to specify the supported > >> types in the signature? > > I agree that we should not introduce (t

Re: [PHP-DEV] [RFC] Attributes v2

2020-03-12 Thread Rowan Tommins
On Thu, 12 Mar 2020 at 03:14, Mike Schinkel wrote: > > The way I was thinking of it, and I think the way this RFC is drafted, > the native attributes would - at least initially - be a very low-level > feature, with libraries expected to build more useful functionality on top. > So if a library ga

Re: [PHP-DEV] Re: [RFC] Userspace operator overloading

2020-03-12 Thread Jan Böhmer
On 11.03.2020 at 10:50, Christoph M. Becker wrote: On 11.03.2020 at 10:22, Nikita Popov wrote: On Fri, Mar 6, 2020 at 9:17 AM Jan Böhmer wrote: Am 02.03.2020 um 15:30 schrieb Nikita Popov: On Thu, Feb 27, 2020 at 9:43 PM wrote: If the operator handler function declares typehints (e.g. p