Re: byte-compiler does *not* complain about missing case or loop

[Jambunathan K]

Andreas Schwab <address@hidden> writes:

> Jambunathan K <address@hidden> writes:
>
>> 2. How would I interpret the error?
>>
>>    1:40 ends points to param line but the actual error report - the
>>    `marker' variable - is elsewhere.
>
> (types . marker) is a malformed function call.

The LINE:COL position of the error report is wrong.

The presence of that defun prevents the "end of data" report from being
triggered.

FWIW, see the attached report

1. With the offending defun compiled in, the "end of data" report is
*absent*.

2. With offending defun ";;"-ed out, the "end of data" report is
*present*.

I wonder what would explain the presence/absence of "end of data"
report.

with-destructuring.txt
Description: Text document

without-destructuring.txt
Description: Text document