Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-03-29 Thread Máté Kocsis
Hi Larry and everyone who took part in the final vs non-final debate, Thought: make the class non-final, but all of the defined methods final, > and any internal data properties private. That way we know that a child > class cannot break any of the existing guarantees, but can still add > conveni

RE: [PHP-DEV] [VOTE] Optional Interfaces

2025-03-29 Thread Juris Evertovskis
Hello, The voting has concluded with 15 votes in favor and 19 against. As such, the RFC has been declined. https://wiki.php.net/rfc/optional-interfaces Thank you all for taking the time to consider the proposal and casting your votes. I'm especially grateful to those who helped refine t

Re: [PHP-DEV] [RFC] Pipe Operator (again)

2025-03-29 Thread Olaf Schmidt-Wischhöfer
Hi Ilija and Larry, thank you so much for your great work bringing PHP forward. I have been passively reading this list for a while and would like to chime in with two thoughts. > Pipes would no longer have the form of expr |> expr, where the > right-hand-side is expected to return a callable.

Re: [PHP-DEV] [RFC] [Discussion] Add WHATWG compliant URL parsing API

2025-03-29 Thread Dennis Snell
> On Mar 25, 2025, at 3:23 PM, Máté Kocsis wrote: > > > Hi Dennis, > > >> I am myself also a bit lost on the countless names that I tried out in the >> implementation, but I think I had toHumanFriendlyString() and >> toDisplayFriendlyString() methods at some point. These then ended up being