aaron.ballman added inline comments.
================
Comment at: clang/include/clang/Basic/Attr.td:3450
+def UseHandle : InheritableParamAttr {
+ let Spellings = [Clang<"use_handle">];
+ let Documentation = [UseHandleDocs];
----------------
xazax.hun wrote:
> aaron.ballman wrote:
> > Should this have a subject limiting it to parameters?
> My understanding was that the subject list is "inherited" from
> InheritableParamAttr, which already has it limited to parameters. Is this not
> the case?
It doesn't seem to be the case looking at Attr.td:557 or thereabouts. Adding
tests for the attributes should clarify whether the change is needed or not,
too.
================
Comment at: clang/include/clang/Basic/AttrDocs.td:4474
+ let Content = [{
+If this annotation is on a function it is assumed to return a new handle.
+In case this annotation is on an output parameter, the function is assumed
----------------
xazax.hun wrote:
> aaron.ballman wrote:
> > What is a "handle"? I think some introduction docs are needed.
> Good point. Do you prefer to copy and paste the introduction to all
> attributes or is it enough to only have it for one of them?
You can set up a documentation category to put all the related attributes
under, and that category can have the introductory documentation. You can see
an example of this with the calling convention attributes. There is a
`DocCatCallingConvs` that is then the `Category` for all the other attributes.
CHANGES SINCE LAST ACTION
https://reviews.llvm.org/D70469/new/
https://reviews.llvm.org/D70469
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
