Anton Bachin
Anton Bachin
I don't see this word in the source. Perhaps you can try looking in upstream projects, like ppxlib and Dune.
For the submodule name, I suggest `Option.Keywords`. It's the most immediately self-explanatory and precise name I've come up with so far.
My preference is to undo the `let*` and `let+` syntax, and to prefer specific decorators on each `let` or other keyword instead, like proposed in https://github.com/facebook/reason/pull/2140. This would do away...
@keleshev made a similar suggestion in https://github.com/ocaml/ocaml/pull/1947#issuecomment-409332752, from which we came up with decorating by a module (whether a good idea or not). There are several additional reasons not to...
@gasche, I'm not making any of these arguments: - That the syntax proposed by Reason is the right one. - That we should give any *weight* to the Reason choice....
No, I didn't explicitly consider this. It should be possible to add with some effort, though. I think my refactoring was mostly orthogonal to this issue.
How should a link to a section be rendered, when there is a link inside the link?
So, to confirm, we allow and retain the nested link for the section itself, but unwrap it for the toc and references?
What is the status of the release at this point?
(For readers here, I replied in the Discuss thread — thanks @nojb).