Document default eagerness of future/promise completions, UPCXX_DEFER_COMPLETION, and new fetching atomic overloads
Issue #486
resolved
As of spec PR 71, the UPC++ spec states that it is implementation defined whether as_future() and as_promise() completions are defer or eager. We need to document this in docs/implementation-defined.md, as well as the UPCXX_DEFER_COMPLETION macro.
Comments (5)
-
reporter
-
reporter
- changed title to Document default eagerness of future/promise completions, UPCXX_DEFER_COMPLETION, and new fetching atomic overloads
-
reporter
A note of the new fetching atomic overloads should also be added to ChangeLog.md.
-
reporter
- changed component to Documentation
-
reporter
- changed status to resolved
Resolved by PR 361.
- Log in to comment
- Assignee
- Type
- Priority
- Status
- resolved
- Component
- Documentation
- Milestone
- 2021.9.0 release
- Version
- Development Branch
- Votes
- 0
- Watchers
- 1
A note of eager futures should also be added to ChangeLog.md.