[Development] Thank you for qScopeGuard

Thiago Macieira thiago.macieira at intel.com
Sun Mar 15 03:25:14 CET 2020

On Friday, 13 March 2020 10:55:29 EST Konstantin Ritt wrote:
> Ah I see Q_DISABLE_COPY(QScopeGuard), so perhaps that's the docu issue.

It's not QScopeGuard that is being copied/moved, but the callable.

You can pass a functor there (like std::function), which needs to be copied 
into the QScopeGuard object before C++17 and mandatory copy elision. That 
functor should not throw when being copied, much less when moving.

Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel System Software Products

More information about the Development mailing list