bug#60450: 30.0.50; Strange behavior of compiler macros in *scratch*

[Gerd Möllmann]

On 31.12.22 15:42, Andreas Schwab wrote:
> On Dez 31 2022, Gerd Möllmann wrote:
>
> > C-j is bound to eval-print-last-sexp, which I wouldn't expect to compile
> > anything, and its doc string doesn't mention anything AFAICS.  Not sure if
> > that's a bug in the code or something missing in the docs.
>
> eval-print-last-sexp uses macroexpand-all.
>
> (macroexpand-all '(foo)) => 1

Right.  And macroexpand-all seems to be closely tied to the compiler, or 
the other way round, depending on one's perspective.  I personally find 
that behavior a bit surprising, but that's just me.  If someone wants to 
close this bug, please do.