In D137205#4225006, @Febbe wrote:

Yes, I agree, while I can't understand, why someone still wants to use only c++11 I can totally understand, that a single Software Engineer can't do anything about this, when the corporation does not permit it.
But it should not be removed, since this warning can still show some pitfalls in performance critical code. A way in c++11 to fix the warning, is to create a functor, instead of a lambda.

Some additional thoughts I had a while ago about something I have raised before:
I think the warnings which can only be fixed with c++14 should either only be issued if that standard was specified or be behind an option. We have lots of lambda captures which could be moved with c++14 and having those warnings would lead to lots of suppressions within the code since we only target c++11.

In D137205#3936944, @firewave wrote:

I still have another false positive with static variables but have not gotten around reducing it yet.

In D137205#3937298, @Febbe wrote:

Does only a warning appear? Or also a fix? Currently, only a warning should appear, but this is not fixable in c++11.

The crash is gone.

I am also experiencing a crash:

#include <string>
#include <list>

Another false positive:

#include <unordered_map>

Getting this false positive:

#include <string>