Stefan
Stefan
Yep, this should be considered a feature, not a bug. If you are testing code that messes with `std::cout` you can simply redirect doctest output via `Context::setCout`.
Does [this](https://github.com/doctest/doctest/blob/master/doc/markdown/stringification.md#translating-exceptions) maybe help?
Could you try defining `_MSC_VER` and `_MSC_FULL_VER` to 0? If not, are you only interested in using full releases? If not I could release a quick prerelease containing a fix,...
Then you'll have to wait for a patch.. So coming back to the prerelease thing, would that work for you?
This is a huge PR, I hope you understand that it will likely take some time to be merged. @philbucher Do you think you will have the time to take...
Actually, leaving this open due to the numerous future considerations.
I very much think this is by design. Why this design was chosen I cannot say. Maybe @onqtam has some insight?
I would like to keep this open to potentially address it in the future. I feel like `MESSAGE` should not trigger previous `INFO` invocations. But it definitely requires some more...
@Trass3r I'm currently in the process of fixing up all of doctest's stringification stuff, which includes a better approach to stringifying types. At first I implemented it via `typeid` and...