Skip to content

Inherit top-comment from @inline includes #654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 14, 2021

Conversation

Julow
Copy link
Collaborator

@Julow Julow commented Mar 30, 2021

Finally closes #478 (this is the last remaining issue).

A signature starting with an include with the @inline tag that doesn't have a top-comment inherits the top-comment from the included module type.

On top of #647. It's changing unrelated code but the expanded documentation would be rendered twice otherwise.

@Julow Julow force-pushed the toplevel-doc-comment-inc branch from 32144f3 to 36c279f Compare March 30, 2021 17:59
@Julow Julow force-pushed the toplevel-doc-comment-inc branch from 36c279f to 2f3e919 Compare April 13, 2021 12:57
@Julow Julow marked this pull request as ready for review April 13, 2021 12:57
@Julow
Copy link
Collaborator Author

Julow commented Apr 13, 2021

Rebased and ready for review.

Julow added 2 commits April 14, 2021 18:47
A signature starting with an `include` with the `@inline` tag that
doesn't have a top-comment inherits the top-comment from the included
module type.
{!modules:...} lists are resolved when linking, code can't be shared
with the generator because types are different too.
@Julow Julow force-pushed the toplevel-doc-comment-inc branch from 2f3e919 to 0171d8e Compare April 14, 2021 16:50
@Julow
Copy link
Collaborator Author

Julow commented Apr 14, 2021

Just rebased :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Top-level doc-comments of module types are discarded
2 participants