From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: SRFI 201 and 202: a reference implelmentation and an invitation to discussion
Date: Tue, 24 Nov 2020 01:37:34 +0100 [thread overview]
Message-ID: <CAMFYt2aDj990=v2JeM_J6czZ+d_m61d+g4q36BKZs32o1TECvw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Hi,
A while ago I proposed a few SRFIs, in particular
https://srfi.schemers.org/srfi-201, which provides extensions to core
bindings (define, lambda, let, let*, or)
https://srfi.schemers.org/srfi-201, which extends SRFI 2 with the
capability of pattern matching
Recently, with a second draft, I have added their implementations for Guile
to SRFI repos:
https://github.com/scheme-requests-for-implementation/srfi-201/
https://github.com/scheme-requests-for-implementation/srfi-202/
I'd like to invite everyone to participate in the discussion, and if it
concludes well, to include the implementation with the distribution
[-- Attachment #2: Type: text/html, Size: 1029 bytes --]
reply other threads:[~2020-11-24 0:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAMFYt2aDj990=v2JeM_J6czZ+d_m61d+g4q36BKZs32o1TECvw@mail.gmail.com' \
--to=godek.maciek@gmail.com \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).