Exactly what it says on the tin!
Details
Details
Diff Detail
Diff Detail
Unit Tests
Unit Tests
| Time | Test | |
|---|---|---|
| 40 ms | Clang.Analysis::Unknown Unit Message ("") |
Event Timeline
Comment Actions
Its worth mentioning that the reason I went out of my way not to change the name associated with reports from CallAndMessage, but I changed all of them here is that NullabilityBase is not a user-facing checker.
Comment Actions
We're observing a surprising disappearance of nullability reports today - like, they didn't just change the name, they disappeared completely. Investigating.
Comment Actions
I landed a lot of patches in the middle of the night, that might be a factor. Say the word if I can help in any way!
Comment Actions
Nope, false alarm! Our buildbot configuration change was at fault. Sorry for forgetting to follow up >.<
clang-format: please reformat the code
- break; // expected-warning {{Nullable pointer is passed to a callee that requires a non-null [nullability.NullableDereferenced]}} - default: { Dummy d = *p; } break; // expected-warning {{Nullable pointer is dereferenced [nullability.NullableDereferenced]}} + break; // expected-warning {{Nullable pointer is passed to a callee that requires a non-null [nullability.NullableDereferenced]}} + default: { + Dummy d = *p; + } break; // expected-warning {{Nullable pointer is dereferenced [nullability.NullableDereferenced]}}