bug#59540: Calling length on a very long improper list is disastrous.

2022-12-12 Thread Ludovic Courtès
Hi, lloda skribis: > I think excessive output is a more serious problem, because it should be > possible to go to a backtrace frame and look at objects directly. On the > other hand, it should also be possible to C-c when guile starts to flood the > terminal. But neither of these workarounds

bug#59540: Calling length on a very long improper list is disastrous.

2022-12-12 Thread lloda
> On 10 Dec 2022, at 18:27, Ludovic Courtès wrote: > > ... > Of these only #2 is something we could work on. However, truncation has > proven to be a hindrance sometimes (in backtraces, objects are > automatically), so I’m not sure we want to enable it by default on > wrong-type-arg error

bug#59540: Calling length on a very long improper list is disastrous.

2022-12-10 Thread Ludovic Courtès
Hi Jeremy, Jeremy Phelps skribis: > I lost my Emacs session today because I accidentally called the length > function on an extremely long improper list. > > But Guile prints the entire thing when it reports the error that happens > when the length function gets to the improper part of the

bug#59540: Calling length on a very long improper list is disastrous.

2022-11-24 Thread Jeremy Phelps
I lost my Emacs session today because I accidentally called the length function on an extremely long improper list. But Guile prints the entire thing when it reports the error that happens when the length function gets to the improper part of the list. It tried to print a few million elements