From: Vladimir Nikishkin <lockywolf@gmail.com>
To: guile-devel@gnu.org
Subject: Call for reviews on srfi-216 SICP Prerequisites.
Date: Wed, 25 Nov 2020 12:27:21 +0800 [thread overview]
Message-ID: <CA+A2iZbfYXOd_BaHZKKujJBFWm8KwSrA=BL0uoyV-B7G1WSvJw@mail.gmail.com> (raw)
Dear GNU Guile developers,
I recently wrote and published SRFI-216, which consists of the
primitives (functions, constants and one special form) that would make
it possible to solve the Structure and Interpretation of Computer
Programs problem set on any scheme system implementing it.
Guile has a special place in the Scheme infrastructure, because it is
likely the most widely used for practical purposes implementation of
all.
So I would like to explicitly invite every interested developer to review
the proposal and to leave comments however small (or critical) they may be.
The document (along with the instructions on how to comment) is here:
https://srfi.schemers.org/srfi-216/
A slightly more updated version would be here:
https://github.com/lockywolf/srfi-216
Thank you for your attention!
--
Yours sincerely, Vladimir Nikishkin
(Sent from GMail web interface.)
reply other threads:[~2020-11-25 4:27 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='CA+A2iZbfYXOd_BaHZKKujJBFWm8KwSrA=BL0uoyV-B7G1WSvJw@mail.gmail.com' \
--to=lockywolf@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).