Larry Garfield
Larry Garfield
As usual, I don't think "never use this fancy new syntax that was just approved" is going to fly. The RFC passed 25 to 4. :-) So let's take "MUST...
Oh! I see what you mean. I'm open to a SHOULD here if the rest of the WG is.
I don't think "you must use this *new* syntax in this way" counts as a BC break. It would only be a BC break if *existing* code suddenly becomes non-compliant...
This has been addressed.
The intent of a style guide isn't just readability, but consistency. I don't recall the last time I saw a capitalized PHP open tag. So making it required that everyone...
Unsurprisingly, my recommendation is for the style used in the RFC. Including allowing get to be all inline if it's an abbreviated get. ```php public string $userName { get =>...
That's true. However: 1. The point of hooks is to make coding easier and more compact for common cases. That means not forcing extraneous newlines where we don't have to....
@iluuu1994 Already in progress: https://github.com/php/doc-en/pull/3898, https://github.com/php/doc-en/pull/3828. More to come.
Added a link to the WIP hooks doc PR.
FFS... I reloaded the page before hitting edit to avoid that! I don't seem to have access to the history diff. (I'm just a member here, not admin.)