Subject: bug#31718: 26.1; Strange behavior of `cond'

From: Ikumi Keita <[email-masked]>
Date: Wed, 06 Jun 2018 14:41:55 +0900

Hi Andreas, thanks for your reply.

>>>>> Andreas Schwab <[email-masked]> writes:
> On Jun 05 2018, Ikumi Keita <[email-masked]> wrote:
>> (defun xyz (arg)
>> "dummy"
>> ;    (cond ((eq arg nil) ; OK
>> ;    (cond ((eq arg 'abc) ; OK
>> ;    (cond ((eq arg 'def) ; OK
>> (cond ((eq arg 'default) ; NG

> The byte-compiler uses 'default as a magic symbol, which breaks this
> case.

Does this mean that this behavior is a (new) designed feature of elisp
and not a bug?
If so, is it the respoisibility of the authors of the codes to rewrite
not to use `default' or else to make sure to set
`byte-compile-cond-use-jump-table' to nil at byte compile?

Best regards,
Ikumi Keita