unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Taylan Kammer <taylan.kammer@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>,
	Guile User <guile-user@gnu.org>
Subject: Re: Starting a GNU Guile awesome list
Date: Tue, 14 Jul 2020 18:37:32 +0200	[thread overview]
Message-ID: <39a1d29c-b102-ffc6-89bb-035dfa758083@gmail.com> (raw)
In-Reply-To: <b9af8fee-cc10-9673-c230-10c0d1ffdb48@posteo.de>

On 13.07.2020 23:19, Zelphir Kaltstahl wrote:
> Hello Guile Users,
> 
> I followed up on that idea I mentioned recently on the mailing list and
> started creating an awesome list:
> 
> https://notabug.org/ZelphirKaltstahl/awesome-guile


Cool!

Let me mention my following projects.  They're in maintenance mode, but
still.


scheme-bytestructures:

https://github.com/TaylanUB/scheme-bytestructures


scheme-srfis

https://github.com/TaylanUB/scheme-srfis/tree/master/srfi

(This contains some SRFIs which aren't implemented in Guile itself, but
since Guile now supports R7RS, you can use these.)

While these are mostly just wrappers for reference implementations, the
SRFI-64 implementation in the repo is IMO superior to the standard one
used by Guile.


- Taylan



      parent reply	other threads:[~2020-07-14 16:37 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-13 21:19 Starting a GNU Guile awesome list Zelphir Kaltstahl
2020-07-13 21:56 ` Jack Hill
2020-07-13 22:56 ` Aleix Conchillo Flaqué
2020-07-14 23:26   ` Zelphir Kaltstahl
2020-07-14  9:00 ` Dmitry Alexandrov
2020-07-14 21:23   ` Zelphir Kaltstahl
2020-07-15  6:32     ` Dr. Arne Babenhauserheide
2020-07-16  8:47       ` Dmitry Alexandrov
2020-07-16 19:01         ` Dr. Arne Babenhauserheide
2020-10-10 12:31         ` Zelphir Kaltstahl
2020-10-10 13:14           ` Matt Wette
2020-10-11  0:57             ` Zelphir Kaltstahl
2020-10-11 19:51               ` Ricardo Wurmus
2020-10-11 23:39                 ` Zelphir Kaltstahl
2020-10-12 10:33                   ` Ricardo Wurmus
2020-11-08 17:09                     ` Zelphir Kaltstahl
2020-11-08 18:55                       ` Paul Smith
2020-12-05 18:15                         ` Zelphir Kaltstahl
2020-07-15  6:36     ` Dr. Arne Babenhauserheide
2020-07-15 21:14       ` Zelphir Kaltstahl
2020-07-15 22:40         ` Dr. Arne Babenhauserheide
2020-07-16  9:18         ` A licence for an ‘awesome list’ (was: Starting a GNU Guile awesome list) Dmitry Alexandrov
2020-07-16 18:56           ` Dr. Arne Babenhauserheide
2020-07-16 18:58             ` Dr. Arne Babenhauserheide
2020-07-16 20:47           ` Zelphir Kaltstahl
2020-07-16 22:55             ` Vladimir Zhbanov
2020-07-16 23:05               ` Vladimir Zhbanov
2020-07-17  0:20             ` John Cowan
2020-07-17  6:43               ` Dr. Arne Babenhauserheide
2020-07-14 14:14 ` Starting a GNU Guile awesome list Dr. Arne Babenhauserheide
2020-07-15 21:24   ` Zelphir Kaltstahl
2020-07-15 22:29     ` Dr. Arne Babenhauserheide
2020-07-14 16:37 ` Taylan Kammer [this message]

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=39a1d29c-b102-ffc6-89bb-035dfa758083@gmail.com \
    --to=taylan.kammer@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=zelphirkaltstahl@posteo.de \
    /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).