Skip to content

fix: handle unicode in lexer #187

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

Merged
merged 2 commits into from
Jan 31, 2025
Merged

fix: handle unicode in lexer #187

merged 2 commits into from
Jan 31, 2025

Conversation

psteinroe
Copy link
Collaborator

@psteinroe psteinroe commented Jan 30, 2025

fixes #184

also using TextSize now. but we might want to revisit the lexer at some point because I dont think we should store the text in the tokens anymore.

@psteinroe psteinroe changed the title fix: handle unicude in lexer fix: handle unicode in lexer Jan 30, 2025
Copy link
Collaborator

@juleswritescode juleswritescode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice!

@psteinroe psteinroe merged commit afd3d19 into main Jan 31, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

lexer: No token found at position
2 participants