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

Document how people can use C++ parser instead of JS one #634

Closed
honzajavorek opened this issue Oct 4, 2016 · 0 comments · Fixed by #668
Closed

Document how people can use C++ parser instead of JS one #634

honzajavorek opened this issue Oct 4, 2016 · 0 comments · Fixed by #668

Comments

@honzajavorek
Copy link
Contributor

It's not very well accessible information, however quite important, because it can significantly affect performance of API Blueprint parsing. Also related to #625 - users should be able to find out which kind of parser they're currently using exactly. Filed as a follow up to #633 (comment), which can be used as a foundation for the actual docs text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant