Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions spec/traits.dd
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,7 @@ $(GNAME TraitsKeyword):
$(GBLINK isFinalClass)
$(GBLINK isPOD)
$(GBLINK isNested)
$(GBLINK isFuture)
$(GBLINK isFloating)
$(GBLINK isIntegral)
$(GBLINK isScalar)
Expand Down Expand Up @@ -192,6 +193,12 @@ $(H2 $(GNAME isNested))
$(DDSUBLINK spec/struct, nested, structs), and
$(DDSUBLINK spec/function, variadicnested, functions).)

$(H2 $(GNAME isFuture))

$(P Takes one argument. It returns `true` if the argument is a symbol
marked with the `@future` keyword, otherwise `false`. Currently, only
functions and variable declarations have support for the `@future` keyword.)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's worth noting that this is an experimental feature. To the point that it's not even @future yet, but @__future (IIRC). Also, I think we should strongly state that this is not intended for user code yet, and link to the DIP.

I think this feature is having too much visibility and too little clarity for an experimental feature...


$(H2 $(GNAME isVirtualFunction))

$(P The same as $(GLINK isVirtualMethod), except
Expand Down