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

Enforce keyword order between override and static/async #43660

Merged
merged 2 commits into from
Apr 15, 2021

Conversation

andrewbranch
Copy link
Member

The order is static override async.

Fixes #43606

@andrewbranch
Copy link
Member Author

Some tests were already using override static. I have literally no opinion on this, aside from that we should enforce an order, since pretty much everything else has an order enforced.

@Kingwl
Copy link
Contributor

Kingwl commented Apr 15, 2021

The current check of modifier order is painful. Are there any possible to map modifiers into some priority. And we just check the order of priority value.

@andrewbranch
Copy link
Member Author

I agree @Kingwl, looking at that function, it’s begging to be refactored into something more declarative. Personally I would love to see something like that implemented.

@DanielRosenwasser
Copy link
Member

@dsherret

@DanielRosenwasser
Copy link
Member

@nicolo-ribaudo

@nicolo-ribaudo
Copy link

Thanks for the heads up @DanielRosenwasser!

@andrewbranch
Copy link
Member Author

Yes 🤦

@Kingwl
Copy link
Contributor

Kingwl commented Apr 27, 2021

🤦

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Author: Team For Milestone Bug PRs that fix a bug with a specific milestone
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Require either async override or override async (don't allow both)
5 participants