[PHP-DEV] [RFC] [Discussion] Clone with

2023-04-16 Thread Máté Kocsis
Hi Everyone, Quite some time after mentioning the "clone with" construct the first time (at the end of the https://wiki.php.net/rfc/write_once_properties#run-time_behaviour section), finally I managed to create a working implementation for this feature which would make it possible to properly modi

Re: [PHP-DEV] Future stability of PHP?

2023-04-16 Thread Larry Garfield
On Mon, Apr 10, 2023, at 10:09 PM, Deleu wrote: > On Mon, Apr 10, 2023 at 7:03 PM Larry > >> >> Again, let's assume there is no question it will happen. The question for >> you: What process for making it happen would you consider sufficiently >> BC-friendly? What timeline? What level of pre-rev

Re: [PHP-DEV] First class callable syntax for instance methods

2023-04-16 Thread Larry Garfield
On Fri, Apr 14, 2023, at 5:52 AM, Zoltán Fekete wrote: > That sure does it, but not that type safe though. Right, which is why I'm fully on board with finding a native syntax way of doing it. (It would be faster, to, without two extra user space function calls.) > The T_BLING (that is the onl

Re: [PHP-DEV] [RFC] New core autoloading mechanism with support for function autoloading

2023-04-16 Thread Dan Ackroyd
On Thu, 13 Apr 2023 at 11:39, Jordi Boggiano wrote: > > On 2023-04-12 22:26, Rowan Tommins wrote: > > I could just about live with that example changing so that the > > fallback was cached, but I definitely don't think an explicit call > > like \foo\strlen('x') should become an implicit alias for

Re: [PHP-DEV] [RFC] New core autoloading mechanism with support for function autoloading

2023-04-16 Thread Dan Ackroyd
On Mon, 10 Apr 2023 at 14:01, Ondřej Mirtes wrote: > > I don’t like the proposed function names: I think we're going to leave thinking about changing the names until the end of the discussion. They don't really matter, and it probably would be better to avoid clogging up the technical discussion