I am trying to get the "unit-threaded" unittesting library to work in an application that uses vibe.d, but am running into some issues.
It seems like unit-threaded is relying on std.concurrency.spawn to create new logical threads for the tests it is going to run, but it seems like vibed is redirecting this to runTask, and runTask seems like it is creating a fiber.
How is this supposed to work? What function in std.concurrency can unit-threaded use and reliably get a thread (where I can later use vibed functionality as a part of my tests)?