Skip to content

Issues: GorNishanov/coroutines-ts

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

21 Open 7 Closed
21 Open 7 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Coroutines and dynamic allocation
#37 opened Jul 22, 2019 by pylorak
6
Lamda Lifetimes And Async Coroutines
#32 opened May 30, 2018 by jumonatr
2
Alternative design for final_suspend that eliminates undefined behaviour of exceptions propagating out of the coroutine internals
#30 opened Feb 9, 2018 by lewissbaker
4
Allow functions to be conditionally compiled as coroutines through use of 'if constexpr'
#29 opened Feb 8, 2018 by lewissbaker
1
give coroutines direct access to their promise
#28 opened Dec 13, 2017 by imoldfella
Allow resume functions to return values
#27 opened Dec 12, 2017 by imoldfella
Suggest explicit placement for coroutine frames
#26 opened Dec 9, 2017 by imoldfella
1
Should coroutine_handle<P1> == coroutine_handle<P2> be allowed?
#25 opened Dec 9, 2017 by lewissbaker
Add 'operator co_await' to 'std::reference_wrapper<T>'
#24 opened Dec 7, 2017 by lewissbaker
Clarify whether get_return_object() result is stored with 'auto' or 'decltype(auto)' semantics
#23 opened Sep 14, 2017 by lewissbaker
LEWG: resume/destroy/operator() should be const (and noexcept)
#22 opened Sep 6, 2017 by GorNishanov
1
LEWG: Cleanup nullptr assignment/ctor for coroutine-handle
#21 opened Sep 6, 2017 by GorNishanov
1
Challenge of shared data between different coroutines and proposal to add coroutine specific shared data infrastructure
#20 opened Aug 30, 2017 by JCYang
4
We should propose a compile time infrastructure to support detection of whether function/object is being co_await on
#18 opened Aug 20, 2017 by JCYang
4
Behaviour of an unhandled_exception() method that throws an exception is under-specified
#17 opened Jul 19, 2017 by lewissbaker
5
[Editorial] Should the example in 8.4.4/11 [dcl.fct.def.coroutine] have its own paragraph number?
#15 opened Jul 14, 2017 by brycelelbach
XX022: Rename [coroutine.handle.import.export] to [coroutine.handle.export.import] for consistency
#14 opened Jun 18, 2017 by GorNishanov
XX025: && parameters in coroutines - very likely result in UB
#13 opened Jun 10, 2017 by GorNishanov
8
XX021: Wording of 'co_return <expr>;' statement for expressions of type void implies that <expr> is not evaluated
#10 opened Mar 11, 2017 by lewissbaker
4
XX028: Separate pre- and post-conditions from Requires: paragraphs
#7 opened Mar 10, 2017 by brycelelbach
1
XX023: Clarify from_address's definition
#6 opened Mar 10, 2017 by brycelelbach
3
ProTip! no:milestone will show everything without a milestone.