(Somehow I missed this, sorry for silence...)
On Wed, Sep 14, 2016 at 6:13 AM Martin Böhme wrote:
> While I'm excited to see this go in anywhere, I have to say I'm a bit sad
> it isn't going in as a warning and instead inside clang-tidy. This has been
> a much requested warning from Clang for ma
>
> While I'm excited to see this go in anywhere, I have to say I'm a bit sad
> it isn't going in as a warning and instead inside clang-tidy. This has been
> a much requested warning from Clang for many years.
>
> Is there a concise description of why this design was chosen? Are there
> specific pr
On Wed, Sep 14, 2016 at 3:38 AM Martin Bohme via cfe-commits <
cfe-commits@lists.llvm.org> wrote:
> Author: mboehme
> Date: Wed Sep 14 05:29:32 2016
> New Revision: 281453
>
> URL: http://llvm.org/viewvc/llvm-project?rev=281453&view=rev
> Log:
> [clang-tidy] Add check 'misc-use-after-move'
>
> Sum
Author: mboehme
Date: Wed Sep 14 05:29:32 2016
New Revision: 281453
URL: http://llvm.org/viewvc/llvm-project?rev=281453&view=rev
Log:
[clang-tidy] Add check 'misc-use-after-move'
Summary:
The check warns if an object is used after it has been moved, without an
intervening reinitialization.
See u
