From: Chris Vine <vine35792468@gmail.com>
To: guile-user <guile-user@gnu.org>
Subject: Re: Fibers 1.1.0 released
Date: Tue, 1 Feb 2022 15:43:23 +0000 [thread overview]
Message-ID: <20220201154323.04d8c1a18ffee1036a521933@gmail.com> (raw)
In-Reply-To: <d87b935668081fe12e37db1c870e87f10c2f6bd8.camel@planete-kraus.eu>
On Mon, 31 Jan 2022 20:09:36 +0100
Vivien <vivien@planete-kraus.eu> wrote:
> Le lundi 31 janvier 2022 à 10:27 -0800, Aleix Conchillo Flaqué a
> écrit :
> > On behalf of the Fibers team, I am very excited to announce Fibers
> > 1.1.0.
> Thank you. Fibers is a very important piece in the guile ecosystem. I
> wish it were part of guile itself. Guile already has futures and
> suspendable i/o out of the box; to me these two features make little
> sense if there’s no Fibers on top of that. What do you think?
Guile's futures have plenty of uses other than fibres - they are a
generic way of offloading computations onto other cores. I may be
wrong, but I don't think they are used by Fibers.
Suspendable ports are essential for practical use of Fibers but there
are other uses of them in asynchronous code, as for example in 8sync and
guile-a-sync.
The main issue with Fibers is that at present it is epoll-only (and so
linux-only). It's great to hear that that is being addressed.
Chris
next prev parent reply other threads:[~2022-02-01 15:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 18:27 Fibers 1.1.0 released Aleix Conchillo Flaqué
2022-01-31 19:09 ` Vivien
2022-01-31 19:31 ` Aleix Conchillo Flaqué
2022-02-01 15:43 ` Chris Vine [this message]
2022-02-01 13:15 ` Dr. Arne Babenhauserheide
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=20220201154323.04d8c1a18ffee1036a521933@gmail.com \
--to=vine35792468@gmail.com \
--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).