Re: question regarding my emacs package

[Madhu <enometh@meer.net>]

* Andrea Corallo <yp1ilbr91x6.fsf @fencepost.gnu.org> :
Wrote on Tue, 13 Jun 2023 04:55:33 -0400:
> Madhu <enometh@meer.net> writes:
>
>> The following works on non-native comp but fails on native-comp.
>>
>> ```
>> (require 'cl-lib)
>> (defun xyz ())
>> (cl-defstruct barf
>>   (buffer-file-name (xyz)))
>>
>> (defun barf-foo ()
>>   (let ((barf (make-barf)))))
>> ```
>
> What's the definition of fail here?

calling M-: (byte-compile-file <file> ) or M-: (native-compile <file>)
on a file with those forms puts me in the debugger backtrace buffer with
the sort of lines I posted upthread.

OK.  I see why others dont see a problem with this. If I call M-x
byte-compile-file or M-x emacs-lisp-native-compile-and-load I only see
this in *Messages* and nothing in *compile-log*

```
Compiling /home/madhu/elisp/debug/barf.el... (make-barf)
Warning: Optimization failure for make-barf: Handler: make-barf--cmacro
(wrong-type-argument stringp (xyz))
Compiling /home/madhu/elisp/debug/barf.el...done
Wrote /home/madhu/elisp/debug/barf.elc
```

So my "errors" were a result of debug-on-error being `t' when evaluating
lisp interactively. So i assume this is not a real problem.