3582c5569d
While looking at some code, I noticed that this warning would show up even if an error for a non-exhaustive when/is shows up for the same when/is expression. This isn't a useful situation to show this warning because things are not exhaustive yet so we should let the user finish and only provide the errors. If things are exhaustive then the code proceeds and if a warning was set when there's only one clause pattern then this warning message can be pushed because that's when it's actually useful. |
||
|---|---|---|
| .. | ||
| aiken | ||
| aiken-lang | ||
| aiken-lsp | ||
| aiken-project | ||
| uplc | ||