EricWF added a comment.
One thing I would like to see in this patch is ensuring the warning doesn't get
generated when the expression appears in unevaluated contexts, such as
`decltype` and `noexcept`. The warning is fundamentally about dataflow, but
this doesn't apply to unevaluated expressions.
There are plenty of cases where a user might want to ask if assignment is well
formed on `noexcept` using only one variable. For example:
template <class T> void foo(T& value) noexcept(noexcept(value = value)) { /*
perform an assignment somewhere */ }
Repository:
rC Clang
https://reviews.llvm.org/D44883
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
