Asherah Connor
Asherah Connor
I've [started the process](https://github.com/github/linguist/pull/4515) for having flow recognised in GitHub -- this means that `.flow` files will be correctly recognised/categorised. We'll need to wait for a bunch more flow repos...
- [ ] Clean up the code. Do a couple once-overs. Look for poor allocation patterns, especially `[]u8` vs `std.ArrayList(u8)` in e.g. `NodeValue.Text`. - [ ] Go through [`TODO`](https://github.com/kivikakk/koino/blob/main/TODO). -...
Verify that these are actually hot in ReleaseFast builds; I think so.
Per cmark, Comrak. See : > A renderer may also provide an option to render soft line breaks as hard line breaks.
We could try reproducing a PEG parser generator like [pest](https://github.com/pest-parser/pest), add Zig output to [re2c](https://re2c.org/), or write manual scanners.
We can model it on the Comrak equivalent: https://github.com/kivikakk/comrak/blob/main/src/cm.rs We should verify roundtripping works for all the CommonMark specs as part of CI.
Broken by 12c32fa. Of course, it does break commonmarker. Currently got Linux/mac builds OK, but working through Windows whatever: https://github.com/gjtorikian/commonmarker/actions/runs/2857777814
See e.g. https://github.com/kivikakk/comrak/actions/runs/5958432069/job/16162659993?pr=337. ``` Run mshick/add-pr-comment@v2 with: message-path: bench-output.md message-id: add-pr-comment refresh-message-position: false repo-owner: kivikakk repo-name: comrak repo-token: *** allow-repeats: false status: success env: CARGO_INCREMENTAL: 0 CARGO_TERM_COLOR: always Error: Resource...
It's become clear to me that Comrak's options and formatting systems are struggling under the weight of what we'd all like it to do slightly differently. Some examples: * AST...