🇨🇦 Kyle HalladayMar 29, 2018
debating whether I want to just say screw it and use standard library threading for my next vulkan experiment, or actually give a shit and use Win32 threads / ditch the standard library altogether.
Show thread🇨🇦 Kyle HalladayMar 29, 2018

on the one hand, I don't really want to worry about containers / Win32 threads, all that jazz.

on the other hand... my hobby projects are all namespaced functions and POD structs...even using vector feels odd. not sure I can handle even more cognitive dissonance.

Show threadruby0x1Mar 29, 2018
@khalladay there's always something like thread.h, single header wrapper style https://github.com/mattiasgustavsson/libs
GitHub - mattiasgustavsson/libs: Single-file public domain libraries for C/C++

Single-file public domain libraries for C/C++. Contribute to mattiasgustavsson/libs development by creating an account on GitHub.

GitHub
Show thread🇨🇦 Kyle HalladayMar 29, 2018
@_discovery I hadn't seen this before, and I now that I have, think this is exactly how I'm going to go (either this header, or a subsequent one). Thanks for the link!
Show threadruby0x1
@khalladay no worries, there's also ones for simple task job based systems and stuff as well iirc, somewhere around. I can't find the link atm
Mar 29, 2018 at 3:15pmWeb