Merged
Conversation
Owner
|
Hey. Thanks for the PRs. I'll have a look at it as soon as i can, i'm a bit more busy with regular work than i'd like to be. |
GB609
requested changes
Mar 19, 2026
Owner
GB609
left a comment
There was a problem hiding this comment.
Thanks again for the contribution. This is actually an annotation I was planning to add as well.
There's only one small change i'd like you to make.
This file contains hidden or 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
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.
Add file- or function-level
@requires. Each@requiresis formatted as an unordered list item and can be multiple lines. I did notice some oddities with indentation of multi-line@requiresand putting them before the@descriptionbut this was consistent with how@std*is handled and@requiresre-uses that code.From the added examples:
is formatted as:
libexample
...
Requires
...
say-hello
My super function
...
Requires