Re: igc, macOS avoiding signals

[Pip Cet]

"Helmut Eller" <eller.helmut@gmail.com> writes:
> (In eval_sub and Ffuncall, it would also help the profiler to move the
> maybe_quit call forward before lisp_eval_depth--. This would only matter
> for interpreted functions, not in byte compiled code.  Curiously,
> apply_lambda doesn't call maybe_quit at all.)

I'm not sure apply_lambda needs to, but if it doesn't, Fprogn should.
(funcall '(lambda () . #1=(t . #1#))) loops without calling maybe_quit.
Checking all calls to Fprogn sounds difficult, so let's put a rarely_quit
in there?

(Paul Eggert fixed some circular-code problems quite a while ago, so I
assume this isn't something we can avoid by making all code non-circular
before executing it)

Pip