Hi @legendecas,
the code it's ok and works, but is it really necessary disallow the copy constructor using a macro?
In this way se avoid to manually disallow the copy constructor in 9 classes, but we will lose in code readability.
What do you think?

@NickNaso I found that this is what's done in Node.js core, v8, and NAN, lots of C++ projects.

It can not be denied that with macros we could not get first sight of what's done after the macro expansion. Yet since disallowing assign/copy/move operations are so commonly used, and I cannot assume it would be easy to write such things every time without missing something. So a macro with a straightforward name describing what it would do will be helpful. And I'd assume it would not be confusing very much on this use case.

@legendecas could you please rebase?

@gabrielschulhof rebased :D

CI:

Landed in 79deefb.