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

Switch to FastParse #121

Open
tabdulradi opened this issue Nov 24, 2016 · 2 comments
Open

Switch to FastParse #121

tabdulradi opened this issue Nov 24, 2016 · 2 comments
Labels
CQL Syntax
Milestone
0.6

Comments

@tabdulradi
Copy link
Member

tabdulradi commented Nov 24, 2016 •
edited
Loading

Although the speed of scala-parser-combinators is not a challenge for Troy (since typically queries are small, one or few lines), Troy still would benifit from Fast parse's tracing feature. This should allow us to implement a user friendly error if malformed CQL has been written by users.
@tabdulradi tabdulradi added this to the 0.6 milestone Dec 18, 2016
@tabdulradi
Copy link
Member Author

Before we can pick this task, we need to ensure 100% coverage under cql-ast and cql-parses sub-projects.

@tabdulradi
Copy link
Member Author

This task is on hold now. Please don't pick it up.

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

No branches or pull requests
1 participant
@tabdulradi