[cfe-dev] Non Static Member Initialization and deleted copy constructor

Steve Ramsey clang at lucena.com
Thu Jul 26 14:23:10 PDT 2012

On Jul 26, 2012, at 1:25 PM, Richard Smith wrote:
> Ouch.
> This isn't restricted to non-static member initializers, it's a problem with the way we instantiate direct-list-initialization in general:

Actually, changing both initializations to assignments (“= 0”) generates the same error (“'std::atomic<int>' invokes deleted constructor”), but for both the class and the template class versions. Needless to say, simply default constructing works in both cases.


More information about the cfe-dev mailing list