Re: [PHP-DEV] Enum + property hook getter

2025-02-08 Thread Marc Bennewitz
Hi Tim, Unintentionally, I first replied to Tim only but it was meant to be send to the list. On 07.02.25 16:11, Tim Düsterhus wrote: Hi Am 2025-02-07 16:03, schrieb Marc Bennewitz: Is that something feasible and how complicated would that be to implement? Supporting this might cause conf

Re: [PHP-DEV] Introduction - Sam Lewis

2025-02-08 Thread Eugene Sidelnyk
Hi Sam, Tim, Rob Maybe there could be another good feature to start with - the function to format bytes into a human-readable format (for debug purpuses) to have pretty view of the size (like 1.5GB, or 20MB) Right now every time I need this, I find myself copying the function from stack overflow,

Re: [PHP-DEV] Introduction - Sam Lewis

2025-02-08 Thread Sam Lewis
Hey Tim Please do not "top-post" on this mailing list. Thank you for the explanation, I saw this in the rules but the Gmail web client did a good job hiding this from me :) > The type of functionality that is nowadays added to PHP’s standard > library is “building block” functionality: Functio

Re: [PHP-DEV] Introduction - Sam Lewis

2025-02-08 Thread Tim Düsterhus
Hi Sam Please do not "top-post" on this mailing list. This means: Please put your reply below the quoted part and ideally also cut the quoted part to the minimum context that you actually want to reply to. You can see how I did this in my first reply to you and also in this reply. On 2/8/25

Re: [PHP-DEV] Introduction - Sam Lewis

2025-02-08 Thread Sam Lewis
Thanks all for sharing your thoughts! I would be happy to review your implementation even if you decide not to > follow through with an RFC (ping @TimWolla on GitHub) I'll definitely take you up on this, thank you. Why stop at temperature though That's fair, maybe that will increase the value p

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

2025-02-08 Thread Gina P. Banyard
On Friday, 7 February 2025 at 04:57, Larry Garfield wrote: > Hi folks. A few years ago I posted an RFC for a pipe operator, as seen in > many other languages. At the time it didn't pass, in no small part because > the implementation was a bit shaky and it was right before freeze. > Nonetheles

Re: [PHP-DEV] Introduction - Sam Lewis

2025-02-08 Thread Rob Landers
On Sat, Feb 8, 2025, at 15:58, Tim Düsterhus wrote: > Hi Sam > > On 2/8/25 15:30, Sam Lewis wrote: > > they wished PHP had built-in functions for converting temperatures between > > Fahrenheit and Celcius, and it seemed like a great small change to learn > > how to contribute to PHP itself. So her

Re: [PHP-DEV] Introduction - Sam Lewis

2025-02-08 Thread Tim Düsterhus
Hi Sam On 2/8/25 15:30, Sam Lewis wrote: they wished PHP had built-in functions for converting temperatures between Fahrenheit and Celcius, and it seemed like a great small change to learn how to contribute to PHP itself. So here I am! That's great. Adding functions definitely is the best way

[PHP-DEV] Introduction - Sam Lewis

2025-02-08 Thread Sam Lewis
Hey everyone, I'm new to the PHP community and have enjoyed learning the language over the past year or so. I saw someone in the Laravel community mention how they wished PHP had built-in functions for converting temperatures between Fahrenheit and Celcius, and it seemed like a great small change

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

2025-02-08 Thread Tim Düsterhus
Hi On 2/8/25 05:05, Larry Garfield wrote: Indeed, precendence and associativity need to be mentioned in the RFC. I've added a precedence section, using examples from the tests and this thread. Associativity is not explicitly spelled out (though only left associativity makes sense). And fo

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

2025-02-08 Thread Tim Düsterhus
Hi On 2/7/25 22:04, Larry Garfield wrote: I split pipes off from the Composition RFC late last night right before posting; I guess I missed a few things while doing so. :-/ Most notably, the Compose section is now removed from pipes, as it is not in scope for this RFC. (As noted, it's going