We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What is the point of writing code like this:
if (IssueBuffer::accepts(new NoEnumProperties( 'Enums cannot have properties', new CodeLocation($this, $prop), $fq_class_name ))) { // fall through }
When it can be written without the if statement:
IssueBuffer::accepts(new NoEnumProperties( 'Enums cannot have properties', new CodeLocation($this, $prop), $fq_class_name ));
The text was updated successfully, but these errors were encountered:
Hey @jack-worman, can you reproduce the issue on https://psalm.dev ?
Sorry, something went wrong.
I see #7020, so I assume that was just an old practice.
It is.
Successfully merging a pull request may close this issue.
What is the point of writing code like this:
When it can be written without the if statement:
The text was updated successfully, but these errors were encountered: