Michael R Fairhurst
Michael R Fairhurst
/test-matrix
Seems like this was closed erroneuosly
This PR is blocked, `codeql run test` automatically adds a `-w` flag during extraction, therefore we cannot create a `\\ COMPLIANT` test case via `codeql run test`. @lcartey Should we...
Tested with MRVA, it finds two issues. 1. [this](https://github.com/torvalds/linux/blob/a430d95c5efa2b545d26a094eb5f624e36732af0/include/uapi/linux/hdreg.h#L38C11-L38C14) appears to be a validly flagged example of relying on implementation-specific behavior. 1. [this macro](https://github.com/torvalds/linux/blob/a430d95c5efa2b545d26a094eb5f624e36732af0/include/uapi/linux/bpf.h#L6206) -- _resulting in dozens of reports,...
Specifically affects RULE-18-6 from MISRA C
It looks like we'll have the same false negative in the case of `-Wformat=0`. This will have to be addressed at the same time in order to satisfy CI/CD tests,...
I wish Dart's null were the `Option` type, and we had a single-parameter-closure shorthand. Then you could just write ``` toPrint.exists(=> print(_)) ```
This could also be easily solved by macros, and the release of macros could include a macro for this. Rust style macro (I think): ``` exists!(toPrint, print(_)) ```
> But Rust can do macro expansion and analysis at compile time. That is not a good approach for a language running on a virtual machine. Dart already has compile-time...
Any solution we have here that's syntax based will likely get really soupy really quick (even `!!`). Named operations are much better as the number of operations increases. If we...