From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: GNU Guile 2.2.0 released
Date: Thu, 16 Mar 2017 17:01:30 +0100 [thread overview]
Message-ID: <87var9xlb9.fsf@gnu.org> (raw)
In-Reply-To: 8760j95xxl.fsf@pobox.com
Hello!
Andy Wingo <wingo@pobox.com> skribis:
> We are delighted to announce GNU Guile release 2.2.0, the first of a
> new stable release series.
>
> More than 6 years in the making, Guile 2.2 includes a new optimizing
> compiler and high-performance register virtual machine. Compared to
> the old 2.0 series, real-world programs often show a speedup of 30% or
> more with Guile 2.2.
Guile 2.2 has gone way beyond what I guess most of us would have
imagined 6 years ago.
A big thank you for pushing Guile this far! Thumbs up to all the
contributors and early adopters of 2.1 as well!
Ludo’.
next prev parent reply other threads:[~2017-03-16 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-16 10:16 GNU Guile 2.2.0 released Andy Wingo
2017-03-16 13:34 ` Nala Ginrut
2017-03-16 14:27 ` Jean Louis
2017-03-18 11:20 ` Ludovic Courtès
2017-03-18 20:50 ` Thomas Morley
2017-03-19 6:52 ` Thomas Morley
2017-03-16 16:01 ` Ludovic Courtès [this message]
2017-03-17 14:19 ` Matt Wette
2017-03-18 2:28 ` Matt Wette
2017-03-17 17:51 ` Jan Wedekind
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=87var9xlb9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).