Should nested comment+code_block be accepted ?

[hhugo]

(**
  This is a comment with code inside
  {[
    (** This is a comment with code inside
        {[ let code inside = f inside ]}
    *)
    let code inside = f inside
  ]}
*)

[aantron]

To clarify, the problem is the nested ]} that is inside the nested (** ... *).

What is the natural scenario in which this kind of input arises?

[hhugo]

This came up while writing tests for ocamlformat.
I don't know if there is a natural scenario for this.
If we don't plan to support it, it would be good to document the restriction.

[aantron]

I'm inclined not to support it, unless we find someone is really using this.

[dbuenzli]

I think we should try, not doing so would prevent the ability of extracting (see #303) any OCaml source file.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. The main purpose of this is to keep the issue tracker focused to what is actively being worked on, so that the amount and variety of open yet inactive issues does not overwhelm contributors.
An issue closed as stale is not rejected — further discussion is welcome in its closed state, and it can be resurrected at any time. odoc maintainers regularly check issues that were closed as stale in the past, to see if the time is right to reopen and work on them again. PRs addressing issues closed as stale are as welcome as PRs for open issues, i.e. they will be given the same review attention, and any other help.