unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Fibers 1.1.1 released
Date: Fri, 3 Jun 2022 21:20:51 -0700	[thread overview]
Message-ID: <CA+XASoUYrMvL57fbkEdwyMVRMb6FX=3O0BfMJ3R6P08zztRdfQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

Hi,

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

This is a bug fix release that fixes an important bug that was causing
tasks waiting on a file descriptor to not be executed in certain cases.
Thank you Ludo for the fix!

The 1.1.1 tarball can be found here:


https://github.com/wingo/fibers/releases/download/v1.1.1/fibers-1.1.1.tar.gz

Its SHA256 sum is:

  597daf696260b5df1ec3ba771d66f4b8858112c1136250b07aaa8099c0c8b351  fibers
-1.1.1.tar.gz

* 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.

Happy Hacking!

Aleix

[-- Attachment #2: Type: text/html, Size: 3619 bytes --]

             reply	other threads:[~2022-06-04  4:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04  4:20 Aleix Conchillo Flaqué [this message]
2022-06-04 13:33 ` Fibers 1.1.1 released 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='CA+XASoUYrMvL57fbkEdwyMVRMb6FX=3O0BfMJ3R6P08zztRdfQ@mail.gmail.com' \
    --to=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).