-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
Change lexing #191
Draft
kaleidawave
wants to merge
27
commits into
main
Choose a base branch
from
merge-lexer
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Change lexing #191
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaleidawave
added
bug
Something isn't working
parser
Related to Ezno's syntax parser, AST definitions and output
v2
Big updates
labels
Aug 16, 2024
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
…ion parse implementation that uses it
- Merge in Expression which keeps existing
probably some other improvements as well
- Rearrange `impl ASTNode` block items - Implementation for tricky handling of arrow functions with return types in ternary conditional expressions - More fixes and "hole" filling to get more complex files parsing
Making some more progress on this:
To add back
To fix
|
- Comments in switch statements - `allow_definite_assignment_assertions`
- More errors in places - A few (still more todo) but better handling in edge cases
- More errors (still non-final) - Change variant name of `default` TS function for `.d.ts` file - Refactor some lexer APIs (add `parse_comment_literal`) - Get parser tests passing - Remove EMPTY from `bracketed_items_from_reader`
- Remove a few more `todo!`s - More clippy fixes
kaleidawave
added
the
compiler-performance
Making parsing / type checking / transformations faster
label
Nov 22, 2024
- Adjust some identifier checks - Move import export parts to subdirectory
kaleidawave
removed
the
compiler-performance
Making parsing / type checking / transformations faster
label
Nov 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will be a long WIP PR to change how lexing works and experiment with some different ideas.
Currently the default mode from the lexer is a lexer in one thread that pushes tokens to a
mspc::channel
and another thread that readsA few reasons
expect_expression
Cannot parse<T>(t: T) => T
under JSX mode (problems with expression prefix) #165Things to change
) ] }
and other things via requested fromexpect_next
.peek()
buffering systemOthers (that might be other prs)
Opening this as a PR at this early stage to track updates and not lose any progress.