bug#36566: 27.0.50; debug is sometimes horribly slow

[Lars Ingebrigtsen <larsi@gnus.org>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

> Maybe it would.  I tend to think we should focus the C code on printing
> data quickly and in a `read`able way (i.e. in sync with `lread.c`) and
> benefit from the comfort of ELisp for the implementation of the
> human-readable version of the printout where performance is not as
> important because we will truncate long outputs anyway.

Well, OK...  but why does edebug use cl-prin1 then when stepping through
code?  Stepping through code should be fast, and we don't really care
that much about the prettiness of the values were displaying then.

Using cl-prin1 would is fine in `edebug-eval-expression' etc, but I
don't quite see the point when stepping?

So if we use prin1 when stepping, we could implement `char-length'
purely as an OVERRIDE element, and not do that in cl-prin1.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no