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

Improve string literal parser #7

Open
iximiuz opened this issue Jul 21, 2021 · 0 comments
Open

Improve string literal parser #7

iximiuz opened this issue Jul 21, 2021 · 0 comments
Labels
good first issue Good for newcomers

Comments

@iximiuz
Copy link
Owner

iximiuz commented Jul 21, 2021

At the moment, the string literal parser is naive. For instance, it doesn't handle escape sequences properly. nom has an example of a more robust string literal parser, so it can be adapted to suit pq use cases. However, the licensing aspect needs to be researched first. Can nom's example be just copied or it has to be copied with the license notice, or it cannot be copied at all?

@iximiuz iximiuz added the good first issue Good for newcomers label Jul 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

1 participant