issues
search
executors
/
futures
A proposal for a futures programming model for ISO C++
22
stars
7
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Interoperability with `std::future`
#79
LeeHowes
closed
6 years ago
4
Rewrite future/promise model section
#78
brycelelbach
closed
6 years ago
2
Change title
#77
LeeHowes
closed
6 years ago
1
Some consistency fixes.
#76
LeeHowes
closed
6 years ago
0
Remove `get_*_future` functions from `standard_promise`
#75
brycelelbach
closed
6 years ago
17
Version 1 bikeshedding
#74
brycelelbach
closed
6 years ago
5
Future and promise type specifications
#73
LeeHowes
closed
6 years ago
0
Use a friend function to specify promise_contract_t default behavior.
#72
chriskohlhoff
closed
6 years ago
2
Remove spurious mentions of execution context.
#71
chriskohlhoff
closed
6 years ago
0
Issue68 executors future dependency
#70
LeeHowes
closed
6 years ago
0
Flesh out interface descriptions for standard_semi_future and standard_continuable_future
#69
LeeHowes
closed
6 years ago
1
Add changes to executors text that depend on Futures
#68
LeeHowes
closed
6 years ago
1
Make FutureContinuation MoveConstructible
#67
LeeHowes
closed
6 years ago
0
SharedFuture postconditions
#66
LeeHowes
closed
6 years ago
0
Add a rendered link to README.md
#65
RedBeard0531
closed
6 years ago
0
Synchronizes with wording and sketch progress mechanism in motivation/design section
#64
brycelelbach
opened
6 years ago
0
Fix typo: exception_tag_t -> exception_arg
#63
jaredhoberock
closed
6 years ago
1
Issue27 shared future
#62
LeeHowes
closed
6 years ago
0
Issue52 blocking operations
#61
LeeHowes
closed
6 years ago
0
Issue 28 cancellation
#60
LeeHowes
closed
6 years ago
0
Add conversion from any future to corresponding future<void>
#59
hkaiser
opened
6 years ago
4
Introduced text describing how continuation is called
#58
LeeHowes
closed
6 years ago
0
.then() should be renamed to avoid breaking code relying on concurrency TS
#57
hkaiser
opened
6 years ago
3
Blocking operations
#56
LeeHowes
closed
6 years ago
2
History section that includes prior art, changelog, and summaries of previous discussions
#55
brycelelbach
opened
6 years ago
2
Notes and polls from the NVIDIA F2F meeting
#54
brycelelbach
opened
6 years ago
0
Add paper number, title, authors, and contributors to paper
#53
brycelelbach
closed
6 years ago
2
Describe `this_thread::future_wait` and `this_thread::future_get` functions
#52
brycelelbach
closed
6 years ago
2
Merge of promise query text into futures paper.
#51
LeeHowes
closed
6 years ago
0
Future execution model guarantees
#50
brycelelbach
closed
6 years ago
6
Added on_error, on_expected, and on_value_or_error
#49
dhollman
closed
6 years ago
12
Add FutureContinuation helper functions to the paper
#48
dhollman
closed
6 years ago
14
Addressed #31
#47
dhollman
closed
6 years ago
0
`std::semi_future` doesn't actually type-erase a `SemiFuture`
#46
dhollman
opened
6 years ago
10
Support passing executors to future continuations
#45
yfeldblum
opened
6 years ago
13
2018-04-26 Afternoon F2F Notes
#44
dhollman
closed
6 years ago
1
`BlockingFuture` concept instead of future waiting functions
#43
brycelelbach
opened
6 years ago
3
`Promise` concept
#42
brycelelbach
closed
6 years ago
3
`std::future` compatibility and interop
#41
brycelelbach
closed
6 years ago
1
Create agenda for 04-26-18 NVIDIA F2F meeting
#40
brycelelbach
closed
6 years ago
0
Create 5 minute intro slide deck for newcomers
#39
brycelelbach
closed
6 years ago
0
Should `SemiFuture`, `ContinuableFuture`, or the concrete future types have an `is_ready` function? An `is_consumed` function?
#38
brycelelbach
opened
6 years ago
0
Extend the exception handling model to support a lightweight option
#37
brycelelbach
opened
6 years ago
15
Presentation for version 1 paper
#36
brycelelbach
opened
6 years ago
0
Finalize logistical details for the 04/26/18 NVIDIA F2F meeting
#35
brycelelbach
closed
6 years ago
2
Create outline for version 1
#34
brycelelbach
closed
6 years ago
1
Should future::then(func) use func(val) or INVOKE(func, val)
#33
RedBeard0531
closed
6 years ago
4
Should callbacks passed to Futures require copyability or can they be move-only?
#32
RedBeard0531
closed
6 years ago
5
Use global-scope traits instead of nested type aliases
#31
brycelelbach
closed
6 years ago
6
Should `UniqueFuture::then` be rvalue-reference qualified?
#30
brycelelbach
closed
6 years ago
15
Previous
Next