@@ -224,6 +224,11 @@ New checks
Recommends the smallest possible underlying type for an ``enum`` or ``enum``
class based on the range of its enumerators.
+- New :doc:`readability-avoid-nested-conditional-operator
+ ` check.
+
+ Finds nested conditional operator.
https://github.com/PiotrZSL edited
https://github.com/llvm/llvm-project/pull/78022
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
https://github.com/PiotrZSL approved this pull request.
LGTM.
Sync first line of release notes, doc, doxygen and could land.
https://github.com/llvm/llvm-project/pull/78022
___
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.or
PiotrZSL wrote:
Personally I think that check for move out of std::unique_ptr, and check for
overall heavy moves could be implemented as an separate one, not related to
unique_ptr. Easiest way to detect heavy moves is to check size of object, and
above some threshold mark them as heavy. But th
PiotrZSL wrote:
Other common example from me:
```
struct SomeHeavyClass {};
std::unique_ptr build();
void sendMsg()
{
auto msgContent = build();
Message msg;
msg.content = std::move(*msgContent);
send(msg);
}
```
And next one:
```
struct Info {
virtual const std::string& get
