Add uncopyable.h, class uncopyable

[rolandreichweinbmw]

No description provided.

[rolandreichweinbmw]

I don't see a way to add a unit test for this feature. It's a convenience feature which being applied incorrectly would not compile.

[rolandreichweinbmw]

If you prefer a unit test including a dummy use of this class (non-functional feature), I can add it.

[jwellbelove]

I've see comments online that Scott Meyers also adds the destructor in his 'Effective C++' book.

[rolandreichweinbmw]

I.e. a non-virtual public "=default" destructor?

Is there a reasoning behind it?

[jwellbelove]

It looks like it is intended to make the destructor protected, rather than default public.

[rolandreichweinbmw]

Added the destructor.

[jwellbelove]

I have sometimes added a commented out unit test that contains 'uncompilable' code, with a surrounding comment that the test should fail to compile if uncommented.
It can be useful if you want to check that the disabled functionality is still disabled after a code change.

[jwellbelove]

I also sometimes do this for static_assert checks.

[rolandreichweinbmw]

I just added the destructor as discussed, and unit tests, including disabled code that intentionally wouldn't compile.