Ichthyostega 67b010ba7e Library: (re)introduce the distinction join / detach ... While it would be straight forward from an implementation POV to just expose both variants on the API (as the C++ standard does), it seems prudent to enforce the distinction, and to highlight the auto-detaching behaviour as the preferred standard case. Creating worker threads just for one computation and joining the results seemed like a good idea 30 years ago; today we prefer Futures or asynchronous messaging to achieve similar results in a robust and performant way. ThreadJoinable can come in handy however for writing unit tests, were the controlling master thread has to wait prior to perform verification. So the old design seems well advised in this respect and will be retained		2023-09-26 01:00:00 +02:00
..
application	Global-Layer-Renaming: adjust namespace qualification	2018-11-15 23:59:23 +01:00
steam	Library: (re)introduce the distinction join / detach	2023-09-26 01:00:00 +02:00
vault	Scheduler: investigate modes of operation	2023-07-03 18:40:37 +02:00
DIR_INFO	re-arrange tests according to layer structure	2013-01-07 05:43:01 +01:00