Jamie Reece Wilson
d520b0ce42
condvars -> cannot matter, you're creating a new object mutex -> cannot mater, you're creating a new object, perhaps copy assignment under lock might be required depending on the parent. either way, a copy ctor is not required semaphore -> copy state in case of the timelime barrier use case. semaphores emulating condvars and similar logic wont mind the overshoot. best case, we do want to copy the previous state as the initial count. worst case, your code is fundamentally broken. |
||
|---|---|---|
| .. | ||
| Aurora | ||
| AuroraAlloc.cpp | ||
| AuroraMacros.hpp | ||
| AuroraRuntime.hpp | ||
| AuroraTypedefs.hpp | ||
| AuroraUtils.hpp | ||