Skip to content

Add a section on trailing commas #18

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.

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

Merged
merged 1 commit into from
Jul 17, 2022
Merged
Changes from all commits
Commits
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
41 changes: 41 additions & 0 deletions spec.md
Original file line number Diff line number Diff line change
Expand Up @@ -117,6 +117,47 @@ Any new types and keywords added to future PHP versions MUST be in lower case.
Short form of type keywords MUST be used i.e. `bool` instead of `boolean`,
`int` instead of `integer` etc.

### 2.6 Trailing commas

Numerous PHP constructs allow a sequence of values to be separated by a comma,
and the final item may have an optional comma. Examples include array key/value pairs,
function arguments, closure `use` statements, `match()` statement branches, etc.

If that list is contained on a single line, then the last item MUST NOT have a trailing comma.

If the list is split across multiple lines, then the last item MUST have a trailing comma.

The following are examples of correct comma placement:

```php
function beep(string $a, string $b, string $c)
{
// ...
}

function beep(
string $a,
string $b,
string $c,
) {
// ...
}

$arr = ['a' => 'A', 'b' => 'B', 'c' => 'C'];

$arr = [
'a' => 'A',
'b' => 'B',
'c' => 'C',
];

$result = match ($a) {
'foo' => 'Foo',
'bar' => 'Bar',
default => 'Baz',
};
```

## 3. Declare Statements, Namespace, and Import Statements

The header of a PHP file may consist of a number of different blocks. If present,
Expand Down