Subject: Re: bug#51368: 29.0.50; `cl-case' should error on incorrect use

From: Stefan Kangas <[email-masked]>
Date: Sun, 24 Oct 2021 05:46:10 -0700

Andreas Schwab <[email-masked]> writes:

> On Okt 24 2021, Philipp Stephani wrote:
>
>> This form demonstrates a few incorrect uses of `cl-case':
>>
>> (cl-case a
>>   (nil 0)   ; doesn't match anything
>>   (t 1)     ; matches everything, but too early
>>   ('foo 2)) ; matches `quote' in addition to `foo'
>>
>> It would be nice if `cl-case' would signal an error or at least warn
>> about these at macroexpansion time, since they are somewhat subtle and
>> easy to get wrong.
>
> clisp errors out on the misplaced `t' clause, but is otherwise silent.

I think it would be good if we could error out on the misplaced t.