From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Guile User <guile-user@gnu.org>
Subject: Re: Guile Steel: a proposal for a systems lisp
Date: Sun, 10 Jul 2022 12:14:55 +0000 [thread overview]
Message-ID: <a9397b65-2937-e502-5222-b57f0aba2841@posteo.de> (raw)
In-Reply-To: <87v8s6xpnq.fsf@dustycloud.org>
I am usually quite far away from the metal and how things work on the bits
level, however, if there was a Guile dialect, or Scheme dialect, which has
similar feel, or maybe can even use Guile libraries, I would find that
interesting. There is probably a lot to learn for me in that area.
I began implementing a bitboard, dreaming about writing a whole chess engine
once and the clever tricks one can use on the bits level were interesting. Maybe
such a thing could also be done in a better way using a Scheme close to the metal.
On 7/9/22 17:35, Christine Lemmer-Webber wrote:
> A little blogpost this morning, not actual software, but software
> desiderata:
> https://dustycloud.org/blog/guile-steel-proposal/
>
> I'd love to see something like the above happen. I'd love to help make
> it happen. So this is more of a call to arms than anything else.
>
> Can we have a "systems lisp"? Can we do better than Rust? Let's put
> some interesting things on that compiler tower of ours!
>
--
repositories: https://notabug.org/ZelphirKaltstahl
next prev parent reply other threads:[~2022-07-10 12:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-09 15:35 Guile Steel: a proposal for a systems lisp Christine Lemmer-Webber
2022-07-10 9:46 ` Blake Shaw
2022-07-10 12:14 ` Zelphir Kaltstahl [this message]
2022-07-11 11:13 ` Tim Van den Langenbergh
2022-07-15 12:08 ` Christine Lemmer-Webber
2022-08-06 22:38 ` Christine Lemmer-Webber
2022-07-11 13:10 ` Martin Becze
2022-08-07 9:28 ` Damien Mattei
2022-08-07 12:43 ` Christine Lemmer-Webber
2022-08-07 14:47 ` Damien Mattei
2022-08-07 16:02 ` Andrew Gwozdziewycz
2022-08-07 20:17 ` Christine Lemmer-Webber
2022-08-07 21:12 ` Damien Mattei
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=a9397b65-2937-e502-5222-b57f0aba2841@posteo.de \
--to=zelphirkaltstahl@posteo.de \
--cc=guile-user@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).