Interesting issue. Was also not fixed in bipt's wip-elisp branch.
Attached is a patch that attempts to fix this, and some related
issues, both for nil and for t.
The strategy is:
1. All Elisp functions we implement in terms of Scheme must be written
to special-handle #nil and #t if they acce
Hi Maxime,
I believe that match conflating () and #nil is the right thing,
even if the current implementation does it unintentionally.
Those two values should be considered "the same" in most situations
even though (eqv? #nil '()) is false.
In fact I think they should be equal? to each other. I
Taylan Kammer schreef op do 13-05-2021 om 21:14 [+0200]:
> Hi Maxime,
>
> I believe that match conflating () and #nil is the right thing,
> even if the current implementation does it unintentionally.
>
> Those two values should be considered "the same" in most situations
> even though (eqv? #nil
On 13.05.2021 22:39, Maxime Devos wrote:
> Taylan Kammer schreef op do 13-05-2021 om 21:14 [+0200]:
>> Hi Maxime,
>>
>> I believe that match conflating () and #nil is the right thing,
>> even if the current implementation does it unintentionally.
>>
>> Those two values should be considered "the sam
Version: 3.0.3
Was fixed in commit ab861be9b.
- Taylan
This seems to have been fixed in the wip-elisp branch.
Note that the branch is a couple years old. There's a version
of the branch by Ricardo Wurmus (rekado) that's been rebased on
a newer version of Guile, though still not on 3.0:
https://git.elephly.net/?p=software/guile.git;a=shortlog;h=refs/
