[Lldb-commits] Use explicit delete in DISALLOW_COPY_AND_ASSIGN

[Zachary Turner via lldb-commits]

Not sure why operator= is returning a const&. It doesn't matter in practice
but it's a bit strange. Anyway lgtm
On Tue, Sep 27, 2016 at 7:11 PM Daniel Austin Noland via lldb-commits <
lldb-commits at lists.llvm.org> wrote:

> Explicit delete is preferable to declaring a method private when
> your intention is to prevent that method from ever being used.
>
> * better compiler error messages
> * can't be bypassed by friendship
> * clearer intent
>
> This was discussed here:
> http://lists.llvm.org/pipermail/lldb-dev/2016-September/011394.html
>
> _______________________________________________
> lldb-commits mailing list
> lldb-commits at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20160928/02a5c3c7/attachment.html>