-
Notifications
You must be signed in to change notification settings - Fork 226
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
chore: Add some docs to the frontend #903
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
More docs are amazing. Gracias!
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
Looks like the Keyword::iter change is failing the CI |
I'm not sure why tbh as it passed in its own PR. Will take a little look. |
Co-authored-by: Tom French <15848336+TomAFrench@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments -- nothing blocking
Related issue(s)
(none)
Description
Summary of changes
Adds some code documentation to the lexer, parser, node interner, and lib.rs files in the frontend.
This is the first part of several PRs to add documentation. I figured they'd be easier to review if I split them up rather than gave a single larger PR.
All changes in this PR are either adding comments or reordering code slightly so that the most important thing in a module is defined first. This later point is to make it easier for readers to find what a module does without having to skip past more unnecessary definitions.