Skip to content

Document how to use aviz #99

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

Merged
Crell merged 2 commits into from
Jan 19, 2025
Merged

Document how to use aviz #99

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b4b67f5
Document how to use aviz.
Crell Oct 15, 2024
5724087
Soften requirements around omitting `public`.
Crell Oct 19, 2024
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
7 changes: 6 additions & 1 deletion spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -659,12 +659,13 @@ engine and language handles them. When present, they MUST be in the following or

* Inheritance modifier: `abstract` or `final`
* Visibility modifier: `public`, `protected`, or `private`
* Set-visibility modifier: `public(set)`, `protected(set)`, or `private(set)`
* Scope modifier: `static`
* Mutation modifier: `readonly`
* Type declaration
* Name

All keywords MUST be on a single line, and MUST be separated by a single space.
All keywords MUST be on a single line, and MUST be separated by a single space. All keywords MUST be all lower-case. The `public` keyword MAY be omitted when using a set-visibility on a public-read property.

The following is a correct example of modifier keyword usage:

Expand All @@ -679,6 +680,10 @@ abstract class ClassName

private readonly int $beep;

protected private(set) string $name;

protected(set) string $boop;

abstract protected function zim();

final public static function bar()
Expand Down