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

Emit trivia as sibling tokens and don't generate a RuleKind for it #737

Closed
5 tasks done
Xanewok opened this issue Jan 11, 2024 · 0 comments · Fixed by #885
Closed
5 tasks done

Emit trivia as sibling tokens and don't generate a RuleKind for it #737

Xanewok opened this issue Jan 11, 2024 · 0 comments · Fixed by #885
Assignees

Comments

@Xanewok
Copy link
Contributor

Xanewok commented Jan 11, 2024

As discussed f2f.

  • Remove LeadingTrivia and TrailingTrivia non-terminals.
  • Include the underlying trivia as siblings to the other rules/tokens in the parent directly.
  • Use FieldName::LeadingTrivia and FieldName::TrailingTrivia for the promoted siblings.
  • Remove fn is_trivia() for RuleKind, since it is impossible for any variant.
  • Implement fn is_trivia() correctly for TokenKind based on Item::Trivia, instead of returning false. (Fix parsing ambiguous call options #862)
@Xanewok Xanewok self-assigned this Jan 11, 2024
@OmarTawfik OmarTawfik mentioned this issue Jan 19, 2024
7 tasks
@OmarTawfik OmarTawfik moved this to Todo in Slang - 2024 H1 Feb 13, 2024
@Xanewok Xanewok moved this from ⏳ Todo to 🔄 In Progress in Slang - 2024 H1 Mar 7, 2024
github-merge-queue bot pushed a commit that referenced this issue Mar 7, 2024
…885)

Closes #737 



Functionally it's done but needs a rebase and a final polish. For now
I'm using the existing PG infra until we clean it up (#638, slated for
this sprint as well).
@github-project-automation github-project-automation bot moved this from 🔄 In Progress to ✅ Done in Slang - 2024 H1 Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant