[PATCH] D18123: Fix implicit copy ctor and copy assignment operator warnings when -Wdeprecated passed.

[David Blaikie via cfe-commits]

UNresolvedSetImpl isn't copy constructible, so should it really be copy
assignable? (it looks like it only needs to be so because of LookupResult -
so once LookupResult is fixed, UnresolvedSetImpl can go back to the way it
was)

Perhaps we should just wait for the fix for LookupResult copying in
SemaStmtAsm from Marina?

Are you planning to cleanup -Wdeprecated in libcxx and libcxxabi too?

I did most of the -Wdeprecated cleanup late last year - but when I tried to
turn it on I hit issues in various stdlibs, etc. It'd be great to finish
the cleanup, or suppress it in system headers, etc, and get it turned on.

On Mon, Mar 14, 2016 at 12:29 PM, don hinton via cfe-commits <
cfe-commits at lists.llvm.org> wrote:

> hintonda added a comment.
>
> Btw, what do you think about making -Wdeprecated the default for
> llvm/clang builds?
>
> With this change, llvm/clang will be clean.  However, libcxx and libcxxabi
> have a bunch of throw warnings.
>
>
> http://reviews.llvm.org/D18123
>
>
>
> _______________________________________________
> cfe-commits mailing list
> cfe-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-commits/attachments/20160314/9b54415f/attachment.html>