Hey all :)
Just a little heads-up that I just landed R7RS support. Thanks to Göran
Weinholt for akku-scm (https://gitlab.com/akkuscm/akku-r7rs/) and
OKUMURA Yuki for yuni (https://github.com/okuoku/yuni), off of which
some of these files were based. (These projects are public domain /
CC0).
The
Wow! Great job!
The text about the standards process is probably going to annoy people since it
does not mention the division between r7rs small and large :)
last time I checked, r7rs large was on path to become a much larger language
than common lisp, and the goal the whole time was a large
Hi,
On Sun 17 Nov 2019 16:52, Linus Björnstam writes:
> The text about the standards process is probably going to annoy people
> since it does not mention the division between r7rs small and large :)
I suppose that is fair, as I am annoyed by R7RS :) However, the report
published in 2013 does
Andy Wingo writes:
> not an error to refer to it as such. In any case, it does not seem to
> me that R7RS-large is similar to the other reports in the RnRS series.
> To me it is more similar in flavor to the SRFI process.
R7RS-large seems to me like an effort to build a foundation for mobility
Hi :)
On Sat 16 Nov 2019 16:26, Ludovic Courtès writes:
> Andy Wingo skribis:
>
>> On Fri 15 Nov 2019 10:03, Ludovic Courtès writes:
>>
>>> I guess we could add a specific ‘&type-exception’ exception or similar,
>>> which would allow us to improve error reporting (that can come later, of
>>> c
