About 15 years ago I was developing a simulation library in C++. There were no coroutines back then, so it was all fibers and threads. It's a lot of fun designing event-driven programs, but it's also a chore debugging them, because execution isn't linear and jumping from place to place, and you definitely don't want to step into scheduler if you want to keep your sanity. Add to that asynchronous threads and it's a nightmare to debug that code, especially if it fails only in optimized build.
Real programmers want a solution which will allow them to make 1000s of syscalls in parallel with little bit of stack memory, not a new syntactical sugar to use heap as stack and easy code writing. Where are the concurrency powers of coroutine?
I agree that the goal for the future should be to move away from MACROS. However, as of today, we still 'need' them. For example, to use __LINE__ (though C++20 offers std::source_location) etc.
About 15 years ago I was developing a simulation library in C++. There were no coroutines back then, so it was all fibers and threads. It's a lot of fun designing event-driven programs, but it's also a chore debugging them, because execution isn't linear and jumping from place to place, and you definitely don't want to step into scheduler if you want to keep your sanity. Add to that asynchronous threads and it's a nightmare to debug that code, especially if it fails only in optimized build.
Example at 29:00 would benefit from a bit more explanation, maybe because IDK what exactly that macro does code is not obvious.
Real programmers want a solution which will allow them to make 1000s of syscalls in parallel with little bit of stack memory, not a new syntactical sugar to use heap as stack and easy code writing. Where are the concurrency powers of coroutine?
It is not really for concurrency but non blocking and reverse of control flow. Try to write iterator over complex datastructure
All good, but..
22:40 Forget about the word "macro" in c++, please. Forever.
If you don't know the benefit of macros please forget about professional programming
I agree that the goal for the future should be to move away from MACROS. However, as of today, we still 'need' them.
For example, to use __LINE__ (though C++20 offers std::source_location) etc.