Catch2: Support thread safety throughout the API

[mwpowellhtx]

I am using INFO, for example, to help record where tests are during execution. This is during a multi-threaded situation: server running in a separate thread. Clients connecting on the parent thread. When I sprinkle INFO throughout client and server code, the program crashes hard.

[repi]

Just ran into the same issue today as well but with REQUIRE, having support for thread safety in the assertion & logging macros would be really nice. For us it wouldn't have to be for all tests but some of our tests are specifically there to verify multithreaded code

[mwpowellhtx]

@repi I'm sure it's for REQUIRE as well. I just called out INFO as a first observation. Point is, thread-safety is A MUST.

[philsquared]

This need is one of the key drivers for Catch2 rebasing on C++11.
Once Catch2 is fully released this will be one of the first major tasks - it's been on the wish-list for a looong time.

[mwpowellhtx]

@philsquared I'd say with the advent of std::thread, there really is no excuse for it to be a wish. In other words, that's not strong enough of a word, IMO.

[philsquared]

Exactly! Before Catch2, and thus C++11, we didn't _have_ std::thread

[repi]

Sweet, we are all in agreement 👍

[mwpowellhtx]

@repi @philsquared Yes, I think we agree on the what. Now is a question of the when, which may necessarily be predicated on the who.

[Leandros]

How is that looking? Just ran into this issue, too.

[capsocrates]

I would love to see this addressed in Catch2.

[mwpowellhtx]

No idea; I've moved on to other non-C++ areas at the moment, so this is not on my radar screen apart from peripheral view.