pfeatherstone

The best thing to do is pinch the storage classes (or write your own), manually write a vtable for each type-erased class (interface thing) and manually write the member methods...

The guts of the type erasure stuff are the storage classes which correctly manage memory, copy constructors and move constructors.

Maybe this isn't an issue since your README specifies Clang16+. Maybe it should be Clang17+ ?

Yes this would be great

@krzysztof-jusiak Also, are you moving development to https://github.com/qlibs/ut ? Or are they two separate things now? I was having trouble getting ut2 to work with runtime tests.

@krzysztof-jusiak Have you had a chance to look at this?

Thank you for your response. I gave qlibs/ut a go but I had to do a lot of fighting in order to get things to compile and run tests at...

Awesome I'll give qlibs an other go later. Otherwise, it would be great to get that bug fixed

Do you think qlibs/ut2 would suffer from the same problem?

I have found other issues with ut2 when using clang https://github.com/qlibs/ut/issues/3