Björn Fahller

OK, good to learn of your progress. Sorry for being a bit inattentive right now, I'm in full panic mode about doing a presentation at the NDC TechTown conference next...

Looking at the build, I see some extraordinarily unexpected warnings. It should build clean from warnings. ``` In file included from D:\a\trompeloeil\trompeloeil\test\compiling_tests.cpp:17: 1>D:\a\trompeloeil\trompeloeil\include\trompeloeil.hpp(1318,13): warning : implicit conversion between pointer-to-function and...

It would be a convenience, but a very dangerous one, because you so easily lose track of what's allowed and what's not. I've spent uncountable hours fixing tests that use...

Ah, I see, I misunderstood. Sorry. Are you using the provided adapter for `doctest`, by using `#include `? It will report all violations using doctest's reporting mechanisms, and does not...

This is a bad situation, and I don't know how to handle it. You really don't want to return here. It would solve the immediate problem of crashing the test...

Marked this as "help wanted". To be honest, I don't think this is currently possible to address without causing even worse problems, but I'm always open to the possibility that...

It's a matter of taste, of course. I think I like the `unique_ptr` version more than communicating via an API. The latter effectively is a singleton which makes life a...

Can you show a small stand alone test program that exposes this problem? On the face of it, I don't understand why there would be a conflict, and my small...

This is largely addressed by commit 76499fd5c41f38a3059fb5c1a35abaaf86d719e5 It gives a good message for what's wrong and where the error is, when the expectation does not match any signature, or is...

Yes, I know. If you haven't provided an adapter for reporting errors, all errors are reported by throwing an exception. I don't know of any other reasonable default, but it...