kevin--
kevin--
just updating from `5feb9c7` to HEAD (`11b4326`) and getting the same error as shown here https://github.com/arximboldi/lager/issues/126#issuecomment-1135780986 Previously building successfully with VS2019 and VS2022 with C++20 enabled and not using deps....
Bisecting indicates that the `origin/futures` work seemed to break MSVC in this fashion -- see `c87a4c7` is the first mainline commit that doesn't build for me
This is a regression from Catch v2.x. I am porting to v3.x today and encountered this error for the first time. IMO it should be solvable by the Catch team.
By the way, found a good work around. Since 3.5.0 you can use `DISCOVERY_MODE` `PRE_TEST` when calling `catch_discover_tests` successfully with Xcode https://github.com/catchorg/Catch2/blob/devel/docs/cmake-integration.md#customization Only downside is you must specify the config...
Sorry for the long delay, here is the info `using TestType = int;` 0. `sizeof(int)` = 4, `alignof(int)` = 4 1. `shared_ptr_stateful_node_size::value` = 44 2. `memory::allocate_shared(pool)` -> `std_allocator::allocate` = n...
Hi @ed95, thanks for the info, but that is not exactly the issue I'm describing. It is rather whether or not `anotherInstanceStarted` is called on initial launch of the app.