Hi On 2/26/25 07:26, Larry Garfield wrote:
I have updated the patch and RFC accordingly. I think you're right, it does make a bit more sense this way.
Is this paragraph in the RFC a left-over from before the change? It appears redundant with the paragraph before:
The pipe operator has a deliberately low binding order, so that most surrounding operators will execute first. In particular, arithmetic operations, null coalesce, and ternaries all have higher binding priority, allowing for the RHS to have arbitrarily complex expressions in it that will still evaluate to a callable. For example:
Best regards Tim Düsterhus
