News for hackers. Stuff that matters.
Re:C++20: Building a Thread-Pool with Coroutines by PaulDavisThe1st on Sunday May 23, 2021 @01:05PM (#27256596)
The first link covers cases most simply described as "it needs to be fast, as fast as possible, but things won't go wrong if there's a random 8msec delay".

Then there's "things will go wrong if there's a random 8msec delay".

Then there's "people will die and/or property will be destroyed if there's a random 8msec delay".

I was referring only to the last two. And yes, that means no malloc.

Re:C++20: Building a Thread-Pool with Coroutines by pjmlp on Sunday May 23, 2021 @04:02PM (#27258056)
Depends how relevant 8msec are on a battleship weapon guidance system,

https://www.ptc.com/en/blogs/plm/ptc-perc-virtual-machine-te...

On any case, that is the reason why I started with depends, just like everyone wants to do big data that fits into a USB floppy, there are those cases where CircuitPython would be more than enough, yet people insist in using Assembly.

In some cases only Ada/SPARK or MISRA will do, others not, yet all of them might fall under real time and embedded deployment.

Re:C++20: Building a Thread-Pool with Coroutines by PaulDavisThe1st on Sunday May 23, 2021 @07:32PM (#27259600)
No, it doesn't depend. That fits clearly into the first category, in which things do not go wrong when there's an 8msec delay.

By contrast, using a DAW with typical settings, an 8 msec delay is catastrophic within the scope of the task, even though nobody gets hurt and nothing gets destroyed.

Re:C++20: Building a Thread-Pool with Coroutines by pjmlp on Monday May 24, 2021 @12:54AM (#27261180)
I guess we are having a language problem here, because when we have three options to refer to, it is obvious that it depends.