diff --git a/.gitignore b/.gitignore index a9d37c56..3aed9fd7 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,5 @@ target Cargo.lock +script/.bundle +script/Gemfile.lock +script/vendor diff --git a/README.md b/README.md index eb73b890..e03acd41 100644 --- a/README.md +++ b/README.md @@ -146,8 +146,8 @@ By default none are enabled; they are individually enabled with each parse by se Comrak's design goal is to model the upstream [`cmark-gfm`](https://github.com/github/cmark-gfm) as closely as possible in terms of code structure. The upside of this is that a change in `cmark-gfm` has a very predictable change in Comrak. -It helps that I maintain both, and tend to update Comrak in lock-step with `cmark-gfm`. Likewise, any bug in `cmark-gfm` -is likely to be reproduced in Comrak. This could be considered a pro or a con, depending on your use case. +Likewise, any bug in `cmark-gfm` is likely to be reproduced in Comrak. This could be considered a pro or a con, +depending on your use case. The downside, of course, is that the code is not what I'd call idiomatic Rust (*so many `RefCell`s*), and while contributors and I have made it as fast as possible, it simply won't be as fast as some other CommonMark parsers @@ -174,7 +174,7 @@ project. Thank you to comrak's many contributors for PRs and issues opened\! -