Does this issue reproduce with the latest release?
What did you do?
What did you expect to see?
A test failure.
What did you see instead?
The test passed.
This might seem like it's not surprising, but:
// Should be no match however currently matches due to:
// Will start failing when this is fixed then just change golden to
// No match pointer indirect
That issue has been fixed for a long time, but apparently it's still matching. I don't yet understand the code's design intent well enough to know whether this comment is wrong, or there's a new/different bug, or ???
The text was updated successfully, but these errors were encountered: