Conversation
Wouldn't it be great to use a ruby peg parser instead of a c peg parser?
|
Have we benchmarked existing Ruby solutions like WikiCloth? |
Author
|
Other developers looked at wiki-cloth before, and found it unsatisfactory both from a completeness and a performance perspective. I'll take a quick re-look at it. |
|
🆒 I'm curious to see how all this pans out. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Wouldn't it be great to use a ruby peg parser instead of a c peg parser?
NOTE: I'm using this as a way of reporting what I'm working on and inviting colleagues to join the discussion (perhaps even to suggest this is a pointless exercise and that I should quit before I spend any time on it). So this pull request is open from the very first commit, rather than once I think it belongs in master.