diff options
| author |  Titus Wormer <tituswormer@gmail.com> | 2022-07-11 11:46:47 +0200 |
|---|---|---|
| committer | Titus Wormer <tituswormer@gmail.com> | 2022-07-11 11:46:47 +0200 |
| commit | c98f902eeae2ac9952173385b146249f11364765 (patch) | |
| tree | 88179439f59608ccde7d32ded1b7dcf1602ccc5e /readme.md | |
| parent | 1fe3139713fb9e5f000af458154ddf634d6ebe64 (diff) | |
| download | markdown-rs-c98f902eeae2ac9952173385b146249f11364765.tar.gz markdown-rs-c98f902eeae2ac9952173385b146249f11364765.tar.bz2 markdown-rs-c98f902eeae2ac9952173385b146249f11364765.zip | |
Add tests for matching identifiers w/ turkish `i`
Diffstat (limited to 'readme.md')
| -rw-r--r-- | readme.md | 3 |
1 files changed, 1 insertions, 2 deletions
@@ -152,8 +152,6 @@ cargo doc --document-private-items - [ ] (5) Do some research on rust best practices for APIs, e.g., what to accept, how to integrate with streams or so? - [ ] (1) Go through clippy rules, and such, to add strict code styles -- [ ] (1) Make sure that rust character groups match CM character groups (e.g., is - `unicode_whitespace` or so the same?) - [ ] (1) Any special handling of surrogates? - [ ] (1) Make sure debugging, assertions are useful for other folks - [ ] (3) Add some benchmarks (against comrak, pulldown-cmark, kramdown?), do some perf testing @@ -274,3 +272,4 @@ important. - [x] (1) Use `char::REPLACEMENT_CHARACTER`? - [x] (3) Add support for concrete constructs (html (flow) or code (fenced) cannot be “pierced” into by containers) +- [x] (1) Make sure that rust character groups match CM character groups |