User Details
- User Since
- Apr 5 2019, 7:04 AM (217 w, 12 h)
Aug 8 2021
Jun 14 2021
This change introduced an MSAN error https://bugs.llvm.org/show_bug.cgi?id=50112
Apr 9 2021
Rebased. Now using native cxxBaseSpecifier and hasDirectBase.
Apr 3 2021
Mar 28 2021
Mar 22 2021
Is this hack actually needed? I could not reproduce a problem with https://bugs.chromium.org/p/chromium/issues/detail?id=860398#c13 repro, the breakpoint fires for me and I see the variable.
Mar 21 2021
Could you please commit the patch for me? I do not have commit rights.
Lint fixes
Mar 19 2021
Forgot to remove a duplicated test
Aug 19 2020
FYI: this breaks some msvc compatibility
template <class> class X {}; template X<int>;
Jun 24 2020
Thanks @zequanwu, much appreciated.
Jun 23 2020
We didn't see it in the code bases I work with, so is boost a special case, or an example of a common practice?
I feel like doing interprocedural analysis for this is overkill. What is the benefit of boost::ignore_unused(foo); rather than the more common (void) foo;? Any examples?
Jun 22 2020
This warning can be turned off by the flag -Wno-uninitialized-const-reference.
This diagnostic bring headaches because frequently -Wunused-variable suppression is done via no-op pseudo-consuming function like [boost::ignore_unused](https://www.boost.org/doc/libs/1_73_0/libs/core/doc/html/core/ignore_unused.html). Particularly, it fires in Boost here https://github.com/boostorg/concept_check/blob/e69c81326d5a4359ac53f9c6fe53fc2baf24df50/include/boost/concept_check.hpp#L135-L141.
Is it possible to make the diagnostic not fire for empty body consuming functions?
Jun 10 2020
May 26 2020
Apr 24 2020
Jan 29 2020
No, I do not have commit rights.
Jan 13 2020
I cannot be a reviewer, just added some dummies questions. And, @spatel, thanks for working on this!
Dec 9 2019
Nov 12 2019
Oct 20 2019
Fixed typo.
Oct 19 2019
Regenerated the docs, added more tests.
Oct 15 2019
Addressed comments.