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

Grammar Tracing support. #267

Closed
bd82 opened this issue Aug 19, 2016 · 2 comments
Closed

Grammar Tracing support. #267

bd82 opened this issue Aug 19, 2016 · 2 comments
Labels
New Feature

Comments

@bd82
Copy link
Member

bd82 commented Aug 19, 2016

Debugging the grammar is easy, but sometimes a little bit of tracing can come in handy as well.
At a minimum console logging should be provided.
More advanced capabilities to consider and investigate:

  • Save an entire Parse flow in memory.
  • ???
@bd82
Copy link
Member Author

bd82 commented Aug 30, 2016

To avoid a performance impact investigate this
https://reaktor.com/blog/javascript-performance-fundamentals-make-bluebird-fast/
3. Use no-op functions and overwrite them lazily to implement costly optional features

@bd82
Copy link
Member Author

bd82 commented Jun 18, 2017

Part of #370

@bd82 bd82 closed this as completed Jun 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
New Feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bd82