-
Notifications
You must be signed in to change notification settings - Fork 323
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
Refactor parser to support precedence change #10516
Comments
Keziah Wesley reports a new STANDUP for today (2024-07-10): Progress: Refactored precedence-resolver to be invariant to spacing contexts. It should be finished by 2024-07-16. Next Day: Next day I will be working on the #10516 task. Work toward applying whitespace-precedence rules within a single precedence-resolver instance. |
Keziah Wesley reports a new STANDUP for yesterday (2024-07-11): Progress: Refactoring operator-section logic. It should be finished by 2024-07-16. Next Day: Next day I will be working on the #10516 task. Switch from spacing-group resolvers to unified resolver. |
Keziah Wesley reports a new STANDUP for today (2024-07-12): Progress: Refactored to unified resolver. One special syntax case remains to be handled, but all other tests are passing. It should be finished by 2024-07-16. Next Day: Next day I will be working on the #10516 task. Implement last syntactic case, some optimization/cleanup/docs. |
Keziah Wesley reports a new STANDUP for yesterday (2024-07-15): Progress: Addressed some edge cases and finished precedence refactor. It should be finished by 2024-07-16. Next Day: Next day I will be working on the #10366 task. New precedence rules. |
Unify space-precedence grouping with operator-precedence resolution. This is the first step of the changes described in #10366.
The text was updated successfully, but these errors were encountered: