My tutorial and take on C++20 coroutines
scs.stanford.edu
My tutorial and take on C++20 coroutines
1–10 of 144 posts
Re: My tutorial and take on C++20 coroutines
#2[deleted]
Re: My tutorial and take on C++20 coroutines
#3Is learning modern C++ worth the effort in 2021?
I know classic c++, but don't really use it anymore.
Re: My tutorial and take on C++20 coroutines
#4I'm a bit confused by all of this.
The idea of coroutines existed since the 60's. Then we came up with OOP that tries to combine function + data. And now we abolished this, are back at only functions and are now solving the 'state capture' problem for functions again with: Coroutines?
How does the history of programming paradigms/patterns make any sense? :)
Good article though.
Re: My tutorial and take on C++20 coroutines
#5Note that the author (in addition to being a great professor) is responsible for one of my favorite papers: https://news.ycombinator.com/item?id=11098655
Re: My tutorial and take on C++20 coroutines
#6Is learning modern C++ worth the effort in 2021? I know classic c++, but don't really use it anymore.
Depends on what you want to use it for. Game programming with UE4 is much nicer with modern c++ syntax, or anything where you want to push the boundaries; but I use kotlin for most things because the syntax is much more concise and the performance isn't an issue.
Re: My tutorial and take on C++20 coroutines
#7I'm a bit confused by all of this. The idea of coroutines existed since the 60's. Then we came up with OOP that tries to combine function + data. And now we abolished this, are back at only functions and are now solving the 'state capture' problem for functions again with: Coroutines? How does the history of programming paradigms/patterns make any sense? :) Good article though.
The glib answer is that these kinds of things are cyclical.
But C++ coroutines don't seem too incompatible with the level of OOP you already get in C++, no?
Re: My tutorial and take on C++20 coroutines
#8I'm a bit confused by all of this. The idea of coroutines existed since the 60's. Then we came up with OOP that tries to combine function + data. And now we abolished this, are back at only functions and are now solving the 'state capture' problem for functions again with: Coroutines? How does the history of programming paradigms/patterns make any sense? :) Good article though.
Objects and coroutines are very closely related.
Re: My tutorial and take on C++20 coroutines
#9I'm a bit confused by all of this. The idea of coroutines existed since the 60's. Then we came up with OOP that tries to combine function + data. And now we abolished this, are back at only functions and are now solving the 'state capture' problem for functions again with: Coroutines? How does the history of programming paradigms/patterns make any sense? :) Good article though.
These are features built into the language designed to make multi-threaded code safer and easier to write.
Re: My tutorial and take on C++20 coroutines
#10From the existing explanations, I’ve deduced that coroutines are a form of continuation based coopetative multitasking. Is it possible to “restart” the sequence, and how would this be done?