From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: guile-user <guile-user@gnu.org>
Subject: Fibers 1.3.0 released
Date: Mon, 29 May 2023 17:23:27 -0700 [thread overview]
Message-ID: <CA+XASoW3vHTSEi6jT=41NU1DBVH-WZ+DEqZKS5d0eq4070_jFg@mail.gmail.com> (raw)
Hi,
On behalf of the Fibers team, I am pleased to announce Fibers 1.3.0.
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
The most exciting change in this release is the replacement of the PSQ
timer queue for a new timer wheel implementation. Thank you Andy! You can
find some details here https://github.com/wingo/fibers/pull/84.
The 1.3.0 tarball can be found here:
https://github.com/wingo/fibers/releases/download/v1.3.0/fibers-1.3.0.tar.gz
Its SHA256 sum is:
569b742dbab5680a9a0bcd70843787dabb713c0cc02eb7f594767d762f65503e
fibers-1.3.0.tar.gz
* Changes since 1.2.0
- Replace PSQ timer queue with new timer wheel.
- Fix libevent cross-compilation issues.
- Always define (getaffinity) and (setaffinity) if not found.
- Rename 'scm_pipe2' to 'scm_fibers_pipe2' to fix a build error with
Guile 3.0.9.
- Fix bit-vector deprecation warnings.
Happy Hacking!
Aleix
next reply other threads:[~2023-05-30 0:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 0:23 Aleix Conchillo Flaqué [this message]
2023-05-30 16:02 ` Fibers 1.3.0 released Aleix Conchillo Flaqué
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+XASoW3vHTSEi6jT=41NU1DBVH-WZ+DEqZKS5d0eq4070_jFg@mail.gmail.com' \
--to=aconchillo@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).