Anton Bachin
Anton Bachin
Removing support for raw text will force us to parse the content of `{% … %}` in odoc, which will require odoc to depend on an HTML parser. I'd say...
Markup.ml is doing the right thing. I added two tests, for unclosed `` in `` with and without whitespace: https://github.com/aantron/markup.ml/blob/c0085e432699c5a0208858850824f8e9ab7f83c6/test/test_html_parser.ml#L448-L479.
@Drup, Markup.ml has a streaming printer – so Lambda Soup does too, it's the `Soup.to_string` function. It can also be done with `soup |> Soup.signals |> Markup.write_html |> Markup.to_something_other_than_string...`. I...
Well, this isn't really due to the PPX primarily – it is due to irregularities in the TyXML interface. However, the PPX might have an opportunity to hackily coerce its...
Yes, I think making this fully composable without inserting run-time coercions isn't going to happen with a PPX.
I think this should be made to work, if possible, since you made the change to how antiquotations are inserted: ``` ocaml let%html to_ocaml = "OCaml" let%html to_tyxml = "TyXML"...
Ok, ``` ocaml let%html links = "" [to_ocaml] "foo" [to_tyxml] "" ```
I think this is (potentially) a great idea, but I don't think TyXML should offer two PPXs as in the attached commits. Ideally, there would be "one great TyXML PPX"...
I think it's best to wait until people use the PPX, and complain about its syntax. Then, we can know if special-casing would be beneficial anywhere. Without user feedback, these...
Seems desirable. I likely won't have time to work on this in the near term.