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.

Sign up for GitHub

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

Jump to bottom

unicode support #156

Open
CrockAgile opened this issue Jan 5, 2025 · 2 comments
Open

unicode support #156

CrockAgile opened this issue Jan 5, 2025 · 2 comments

Comments

@CrockAgile
Copy link
Collaborator

CrockAgile commented Jan 5, 2025 •
edited
Loading

A contributor was unclear while working on #154 if the crate supported unicode (link).

Documentation and tests should call this out that BNF intends (and should?) support unicode.
@Carlyle-Foster
Copy link
Contributor

i think that we should definitely support grammars that operate on unicode, but for the grammar definitions themselves limiting unicode support to terminals could be an avenue for performance gains + make the code a bit simpler (both in human and machine terms)

@Carlyle-Foster
Copy link
Contributor

it's not a pressing issue though, rn i think we handle unicode correctly and use it everywhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@CrockAgile @Carlyle-Foster