-
Notifications
You must be signed in to change notification settings - Fork 53
Open
Labels
!discussNeeds discussion (at meeting or online)Needs discussion (at meeting or online)non-breakingDoes not require a breaking change (that would block V1.0)Does not require a breaking change (that would block V1.0)
Description
In wgpuInstanceWaitAny, uint64_t timeoutNS can be set to a very large value to effectively have no timeout (infinite timeout). Typically UINT64_MAX would be used for this, though technically that's not a sentinel value, it's just a request for a 584-year timeout.
However implementations may optimize large timeout values by avoiding some work (like setting an OS timer or calling setTimeout), so there is some meaning in large values - of course UINT64_MAX is the best guarantee of hitting such optimizations.
Should we #define an "infinite timeout" or "max timeout" constant as UINT64_MAX, as a semantic name for this purpose? (Non-breaking change.)
Kangz
Metadata
Metadata
Assignees
Labels
!discussNeeds discussion (at meeting or online)Needs discussion (at meeting or online)non-breakingDoes not require a breaking change (that would block V1.0)Does not require a breaking change (that would block V1.0)