This is currently a known issue; this is not a mistake, but a quality problem.
The problem boils down to irrefutable coincidences, that is:
match variable { 1 => 2, i => 2 * i }
Here i is an irrefutable match, that is, it always matches, regardless of the value of variable .
Well, we have the same problem with this strange report: because Unknown unknown, it becomes the name of the variable in an irrefutable match! Of course, this is unintentional, but it makes sense to the compiler.
The good news is that the compiler starts complaining right after the next match, so you can easily find out which match is irrefutable.
Expected
There are many variations of this error (see duplicates), it can also be caused by improper enum import and, therefore, not having its own options in scope.
Matthieu M.
source share