From: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-user <guile-user@gnu.org>, guile-devel@gnu.org
Subject: Re: Fibers 1.1.1 released
Date: Sat, 04 Jun 2022 15:33:06 +0200 [thread overview]
Message-ID: <878rqcwk4b.fsf@web.de> (raw)
In-Reply-To: <CA+XASoUYrMvL57fbkEdwyMVRMb6FX=3O0BfMJ3R6P08zztRdfQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]
Aleix Conchillo Flaqué <aconchillo@gmail.com> writes:
> On behalf of the Fibers team, I am excited to announce Fibers 1.1.1.
>
> Fibers is a lightweight concurrency facility for Guile that supports non-blocking input and output, millions of concurrent threads, and Concurrent
> ML-inspired communication primitives. For more information, see the web version of the manual at:
>
> https://github.com/wingo/fibers/wiki/Manual
> * Changes since 1.1.0
>
> - Always add file descriptors finalizer in (schedule-task-when-fd-active).
> - Do not load 'epoll.so' during cross-compilation.
> - Pass '--target' and '-L' to 'guild compile' when cross-compiling.
> - Do not refer to 'epoll.so'-provided variables at expansion time.
> - Install .go files to …/site-ccache, not …/ccache.
Very cool! Thank you for the release!
I use fibers in dryads wake,¹ and it allowed me to wrap my head around
mapping websockets to standard input and output without running into
concurrency problems, and that’s pretty awesome!
¹: https://dryads-wake.1w6.org
Best wishes,
Arne
--
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1125 bytes --]
prev parent reply other threads:[~2022-06-04 13:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-04 4:20 Fibers 1.1.1 released Aleix Conchillo Flaqué
2022-06-04 13:33 ` Dr. Arne Babenhauserheide [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=878rqcwk4b.fsf@web.de \
--to=arne_bab@web.de \
--cc=aconchillo@gmail.com \
--cc=guile-devel@gnu.org \
--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).