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
Ah I see Q_DISABLE_COPY(QScopeGuard), so perhaps that's the docu issue.
Regards,
Konstantin
пт, 13 мар. 2020 г. в 18:38, Konstantin Ritt :
> I just noticed the documentation says
> > The callable shouldn't throw when executed, copied or moved.
> , which brings a question: is there really a
I just noticed the documentation says
> The callable shouldn't throw when executed, copied or moved.
, which brings a question: is there really a particular reason to copy
QScopeGuard instance? what the expected behavior for the instance copy
then, call f in some other place?
Regards,
Konstantin
On Friday, 21 February 2020 06:02:29 PST NIkolai Marchenko wrote:
> it's definitely neat, but it's nothing that you can't do with pure c++
> though. It's just qt's native implementation of score guard pattern. Tbh I
> didn't even know it existed because I use my own scope guarder class.
The
On 2020-02-21 15:02, NIkolai Marchenko wrote:
it's definitely neat, but it's nothing that you can't do with pure c++
though. It's just qt's native implementation of score guard pattern.
Tbh I didn't even know it existed because I use my own scope guarder
class.
On Fri, Feb 21, 2020 at 4:33
it's definitely neat, but it's nothing that you can't do with pure c++
though. It's just qt's native implementation of score guard pattern. Tbh I
didn't even know it existed because I use my own scope guarder class.
On Fri, Feb 21, 2020 at 4:33 PM Henry Skoglund wrote:
> Hi, just want to thank
Hi, just want to thank whoever worked to implement qScopeGuard (in
5.12), it was a perfect gift from heaven today :-)
I'm writing a LOB app with heavy database munging, and want to show the
user an hourglass cursor while munging/waiting for MS SQLServer.
However my functions have lots of exits
