Skip to content

Expand Section 2.5 entry in the PER-CS 2.0 to 3.0 migration guide #148

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
rodrigoprimo wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Expand Section 2.5 entry in the PER-CS 2.0 to 3.0 migration guide #148

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 4 additions & 1 deletion migration-3.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,10 @@ is the canonical source for the PER-CS formatting expectations.
Formatting conventions are now provided for compound types (those that include union or intersection type declarations).

* The `|` and `&` symbols and parentheses MUST NOT have leading or trailing spaces.
* If a type declaration is long enough to split to multiple lines, each ANDed block must be on one line, and each ORed block on its own line.
* If a type declaration is long enough to split to multiple lines:
* If the type is only unions or only intersections, each line holds a single type.
* If it mixes both, each line holds one union segment, with that segment's intersected types kept together.
* The symbol on which it is split MUST be at the start of each line.
* If one of the types listed is `null`, it must come last.
* Favor `?` over `|null` in cases where both work.
* A multi-catch statement must follow the same rules. (See section 5.6 as well.)
Expand Down