Skip to content
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

Make use statements redundant #10256

Merged
merged 1 commit into from
Nov 27, 2022

Conversation

greg0ire
Copy link
Member

In 68bc00b, while fixing coding style, I introduced many, many use statements in that file. Using half-qualified names sometimes, and unqualified names some other times makes no sense.

If AST\ is used at least once, use it always.

In 68bc00b, while fixing coding style,
I introduced many, many use statements in that file. Using
half-qualified names sometimes, and unqualified names some other times
makes no sense.

If AST\ is used at least once, use it always.
Copy link
Member

@SenseException SenseException left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wouldn't mind the many use statements.

@greg0ire greg0ire added this to the 2.14.0 milestone Nov 27, 2022
@greg0ire
Copy link
Member Author

I find it's a bit much, but also, since this was the original style, I elected to pick that one to eliminate the inconsistency.

@greg0ire greg0ire merged commit d5ef6be into doctrine:2.14.x Nov 27, 2022
@greg0ire greg0ire deleted the parser-consistent-style branch November 27, 2022 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants