Add {!type:…} annot in docs to help odoc with ambiguities
#296
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It's possible that a type and a value share the same name in generated code, and odoc can't know which of them the reference is pointing to.
MisterDA
requested review from
rgrinberg,
mjambon,
Khady,
zindel and
cyberhuman
as code owners
mjambon
added a commit
to mjambon/opam-repository
that referenced
this pull request
Jun 7, 2022
…n-codec-runtime and atd (2.8.0) CHANGES: * atdgen: use odoc syntax to disambiguate clashing names (ahrefs/atd#296) * atdpy: propagate decorators on sum types to all constructor classes (ahrefs/atd#298)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It's possible that a type and a value share the same name in generated
code, and odoc can't know which of them the reference is pointing to.