On 14.05.2021 15:34, Taylan Kammer wrote:
>
> It might also be good, in addition, to make the Scheme writer
> write (foo . #nil) as (foo . #nil). The positive is that it
> would make bugs in Elisp compatibility easier to see by not
> masking the fact that one has #nil instead of () at the end
> o
I believe it would be better if #nil were equal? to ().
It would keep *not* being equal? to #f and as such not disturb the
property of transitiveness.
Making #nil and () be equal? would be a lot more intuitive since
they both represent the empty list, and since equal? is commonly
used to test the
Severity: minor
Hi guilers,
I have some trouble making backtraces with system-async-mark.
(Not encountered in ‘real code’, only when playing with the REPL.)
From a REPL:
scheme@(guile-user)> (system-async-mark backtrace )
Backtrace:
Exception thrown while printing backtrace:
In procedure progr
I just noticed someone sent a patch that seems relevant here
It's in #43102
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43102
Hi Zefram,
this is an interesting issue. Here's a related one:
https://bugs.gnu.org/48318
I think first of all #nil and '() should actually be equal?
to each other. After all, both represent the empty list,
and checking structural equality between lists is one of the
common uses of equal?.
in Guile 3.0.5 installed with Guix (as a package manager on top of
Ubuntu)
In a file I have this simple procedure
(define (f n)
(if (< n 3)
n
(+ (f (- n 1))
(* 2 (f (- n 2)))
(* 3 (f (- n 3))
it's a variation of the one calculating the Fibonacci numbers, from
