3 ms·

Very disappointed that coroutines will be included in their present form. Did the committee just want to push something out?

smallstepforman 8y ago
A good solution today is better than a potentially better solution tomorrow.
- jcelerier 8y ago
  it really depends. if the accepted coroutines hides memory allocations willy-nilly, it means that there is a whole body of code that will never ever use coroutines in their code. While waiting for non-magic-allocating coroutines would have made those better in five years.
mattnewport 8y ago
"Coroutines (Gor Nishanov) was adopted for C++20. A number of other authors that have their own coroutine proposals have also done great work to give feedback to this design and inform the committee in the process of showing their own designs, and the adopted coroutines design is expected to adopt some of their additional programming capabilities in the future as well as we continue to build on it after C++20. At this meeting, we had many detailed design discussions, including notably these papers that will be available in a few weeks when the post-meeting mailing is posted: a unified consensus report from all coroutines proposers describing the strengths and weaknesses of all their proposals, and a consensus report from implementers from all major C++ compilers about the tradeoffs and feasibility of the basic facilities required by the various coroutines proposals. Both of these papers are very educational and highly recommended." https://herbsutter.com/2019/02/23/trip-report-winter-iso-c-standards-meeting-kona/ https://herbsutter.com/2019/02/23/trip-report-winter-iso-c-s... The papers aren't available yet but presumably will explain the reasoning behind accepting them in their current form.
alexeiz 8y ago
If you want your opinion heard, you have to participate. The problem though, is that certain people have pretty much a full-time job to push stuff through the committee. So they invest way more time than you can ever afford. And in the end they get their shit into the Standard.

smallstepforman 8y ago

A good solution today is better than a potentially better solution tomorrow.

jcelerier 8y ago
it really depends. if the accepted coroutines hides memory allocations willy-nilly, it means that there is a whole body of code that will never ever use coroutines in their code. While waiting for non-magic-allocating coroutines would have made those better in five years.

mattnewport 8y ago

"Coroutines (Gor Nishanov) was adopted for C++20. A number of other authors that have their own coroutine proposals have also done great work to give feedback to this design and inform the committee in the process of showing their own designs, and the adopted coroutines design is expected to adopt some of their additional programming capabilities in the future as well as we continue to build on it after C++20. At this meeting, we had many detailed design discussions, including notably these papers that will be available in a few weeks when the post-meeting mailing is posted: a unified consensus report from all coroutines proposers describing the strengths and weaknesses of all their proposals, and a consensus report from implementers from all major C++ compilers about the tradeoffs and feasibility of the basic facilities required by the various coroutines proposals. Both of these papers are very educational and highly recommended." https://herbsutter.com/2019/02/23/trip-report-winter-iso-c-standards-meeting-kona/ https://herbsutter.com/2019/02/23/trip-report-winter-iso-c-s... The papers aren't available yet but presumably will explain the reasoning behind accepting them in their current form.

alexeiz 8y ago

If you want your opinion heard, you have to participate. The problem though, is that certain people have pretty much a full-time job to push stuff through the committee. So they invest way more time than you can ever afford. And in the end they get their shit into the Standard.