From: "Thompson, David" <dthompson2@worcester.edu>
To: Guile User <guile-user@gnu.org>
Subject: [ANN] Guile Hoot 0.4.0 released!
Date: Tue, 9 Apr 2024 10:12:46 -0400 [thread overview]
Message-ID: <CAJ=RwfY6mYmiDBfPiLHxgHDyv_m=V0ACcZaBme-vtSA_Qs4krg@mail.gmail.com> (raw)
Hey Guilers!
On behalf of the Spritely Institute, I'm happy to announce that Guile
Hoot v0.4.0 has been released! Hoot is a Scheme to WebAssembly
compiler backend for Guile, which means you can now run Scheme in the
browser for real, tail calls and all.
The highlights of this release are:
* Hoot now supports user-defined modules. Users no longer have to
stuff their entire program into one file!
* The standard library is now available as a collection of importable
modules. Hoot provides the R7RS (scheme ...) namespace, as well as
its own (hoot ...) namespace.
* An example project was added to the source tree in Git to serve as
an easy starting point for new Hoot projects. This example project
also ships with our official release tarballs. See the template's
README [0] for more information.
* More of R7RS-small has been implemented and Hoot can now run 54 out
of 57 Scheme benchmarks! [1] (Note that this data is currently just
from my machine. The official benchmark server will need to be
capable of running NodeJS 22+, or another V8 distro, before Hoot
results could be published there.)
Read the full release notes here:
https://spritely.institute/news/guile-hoot-v040-released.html
If you use Guix then it's easy to try out Hoot:
guix pull
guix shell guile-next guile-hoot
Happy hooting!
- Dave
[0] https://gitlab.com/spritely/guile-hoot/-/blob/main/examples/project-template/README.md?ref_type=heads
[1] https://ecraven.github.io/r7rs-benchmarks
next reply other threads:[~2024-04-09 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 14:12 Thompson, David [this message]
2024-04-09 14:59 ` [ANN] Guile Hoot 0.4.0 released! Luis Felipe
2024-04-09 22:37 ` Nala Ginrut
2024-04-09 23:17 ` Thompson, David
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='CAJ=RwfY6mYmiDBfPiLHxgHDyv_m=V0ACcZaBme-vtSA_Qs4krg@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--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).