Confusing coverage result: Uncovered argument for match
#3456
Labels
[C] Bug
This is a bug. Something isn't working.
[E] User Experience
An UX enhancement for an existing feature. Including deprecation of an existing one.
[F] Spurious Failure
Issues that cause Kani verification to fail despite the code being correct.
Z-UnstableFeature
Issues that only occur if a unstable feature is enabled
We noticed a confusing coverage result in #3119 where, for the code
we get the result
which is confusing because it reports the
dir
inmatch dir {
asUNCOVERED
. It's not clear to me why this is happening, but we should at least check if this is also the case for a standard execution with coverage.The text was updated successfully, but these errors were encountered: