You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this for new documentation, or an update to existing docs?
New
Describe the incorrect/future/missing documentation
CCCL macros are very curated and are tested across many configurations in all projects that adopt CCCL.
Some examples:
host/device: _CCCL_HOST_DEVICE
standard attributes: _CCCL_FALLTHROUGH, _CCCL_NODISCARD
compiler macros: _CCCL_CUDA_COMPILER
buildins: _CCCL_HAS_BUILTIN
dialects: _CCCL_STD_VER,
etc.
These macros can be documented and exposed to users
If this is a correction, please provide a link to the incorrect documentation. If this is a new documentation request, please link to where you have looked.
Exposing those macros to users prevents us from ever changing them again if need be. We recently spend a lot of time cleaning up our internal infrastructure and its been a pain to have to ensure backwards compatibility with publicly exposed Thrust and CUB macros.
that's true, backwards compatibility is problematic. However, we should at least list these macros (or a subset of them) somewhere. As an external user, I would prefer taking the risk even if internal only instead of reimplementing many of them, at least initially...
Is this a duplicate?
Is this for new documentation, or an update to existing docs?
New
Describe the incorrect/future/missing documentation
CCCL macros are very curated and are tested across many configurations in all projects that adopt CCCL.
Some examples:
_CCCL_HOST_DEVICE
_CCCL_FALLTHROUGH
,_CCCL_NODISCARD
_CCCL_CUDA_COMPILER
_CCCL_HAS_BUILTIN
_CCCL_STD_VER
,These macros can be documented and exposed to users
If this is a correction, please provide a link to the incorrect documentation. If this is a new documentation request, please link to where you have looked.
https://nvidia.github.io/cccl/libcudacxx/extended_api/macro.html
The text was updated successfully, but these errors were encountered: