aboutsummaryrefslogtreecommitdiffstats
path: root/readme.md
diff options
context:
space:
mode:
authorLibravatar Titus Wormer <tituswormer@gmail.com>2022-06-16 19:04:16 +0200
committerLibravatar Titus Wormer <tituswormer@gmail.com>2022-06-16 19:04:16 +0200
commit60ea2fd3a09f10fa28bf48575736b47afebf3221 (patch)
treef7aae5cec9181f7ff5df23e648fe1da22a94209f /readme.md
parentef14d6581848ba5052d3389bb61fc96645551eef (diff)
downloadmarkdown-rs-60ea2fd3a09f10fa28bf48575736b47afebf3221.tar.gz
markdown-rs-60ea2fd3a09f10fa28bf48575736b47afebf3221.tar.bz2
markdown-rs-60ea2fd3a09f10fa28bf48575736b47afebf3221.zip
Add heading (setext)
Diffstat (limited to '')
-rw-r--r--readme.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/readme.md b/readme.md
index 0cbff1e..20ce174 100644
--- a/readme.md
+++ b/readme.md
@@ -46,8 +46,6 @@ cargo doc --document-private-items
### Some major obstacles
-- [ ] (1) Setext headings: can they be solved in content, or do they have to be
- solved in flow somehow
- [ ] (8) Can content (and to a lesser extent string and text) operate more
performantly than checking whether other flow constructs start a line,
before exiting and actually attempting flow constructs?
@@ -114,7 +112,7 @@ cargo doc --document-private-items
- [x] hard break (escape)
- [x] hard break (trailing)
- [x] heading (atx)
-- [ ] (1) heading (setext)
+- [x] heading (setext)
- [x] html (flow)
- [x] html (text)
- [ ] (3) label end
@@ -135,11 +133,11 @@ cargo doc --document-private-items
- [x] code (indented)
- [x] content
- [x] heading (atx)
+ - [x] heading (setext)
- [x] html (flow)
- [x] thematic break
- [ ] (3) content
- [ ] definition
- - [ ] heading (setext)
- [x] paragraph
- [ ] (5) text
- [ ] attention (strong, emphasis) (text)
@@ -169,6 +167,8 @@ cargo doc --document-private-items
- [x] (1) Add examples to `CompileOptions` docs
- [x] (3) Fix deep subtokenization
- [x] (1) text in heading
+- [x] (1) Setext headings: can they be solved in content, or do they have to be
+ solved in flow somehow
### Extensions