Skip to content

Generalize double arrow spacing rule #157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
samdark wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Generalize double arrow spacing rule #157

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
91d20fb
Generalize double arrow spacing rule
samdark Aug 27, 2026
765e2ea
Clarify alignment around double arrows
samdark Aug 27, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -924,7 +924,6 @@ For a `set` hook, if the argument name and type do not need to be redefined, the

If a hook consists of a single expression, then PHP allows it to be shortened using `=>`. In that case:

* There MUST be a single space on either side of the `=>` symbol.
* The body MUST begin on the same line as the hook name and `=>`.
* Wrapping is allowed if the expression used allows for wrapping, using the rules defined elsewhere in this document.

Expand Down Expand Up @@ -1302,8 +1301,10 @@ try {

Style rules for operators are grouped by arity (the number of operands they take).

When space is permitted around an operator, multiple spaces MAY be
used for readability purposes.
When space is permitted around an operator or the `=>` symbol, multiple spaces
MAY be used for readability purposes.

The `=>` symbol MUST be preceded and followed by at least one space.

All operators not described here are left undefined.

Expand Down Expand Up @@ -1528,8 +1529,6 @@ and principles as long closures above, with the following additions.

The `fn` keyword MUST NOT be succeeded by a space.

The `=>` symbol MUST be preceded and succeeded by a space.

The semicolon at the end of the expression MUST NOT be preceded by a space.

The expression portion MAY be split to a subsequent line. If so, the `=>` MUST be included
Expand Down