From: Maxime Devos <maximedevos@telenet.be>
To: "Linus Björnstam" <linus.internet@fastmail.se>,
"Damien Mattei" <damien.mattei@gmail.com>,
guile-user <guile-user@gnu.org>,
guile-devel <guile-devel@gnu.org>
Subject: Re: Scheme+
Date: Mon, 20 Dec 2021 17:33:11 +0000 [thread overview]
Message-ID: <7706b14ef6319e7784ee73a74ec399db28751c53.camel@telenet.be> (raw)
In-Reply-To: <14e10823-2655-48c2-9736-383708da492e@www.fastmail.com>
Linus Björnstam schreef op ma 20-12-2021 om 09:15 [+0100]:
> I played around with it and it seems to rely heavily on mutation,
> which makes guile (and chez and racket for that matter) box the
> values. That adds a layer of indirection to memory access, meaning
> slower code (apart from the more obvious problems of continuation
> safety and threading safety).
Concerning thread-safety and continuation safety: as long as
continuations aren't resumed multiple times (*), and as long as no
closures are passed, then the mutation doesn't make any observable
difference (except fastness).
(*) E.g., the continuations that guile-fibers construct are resumed
only once.
Greetings,
Maxime.
prev parent reply other threads:[~2021-12-20 17:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 0:05 Scheme+ Damien Mattei
2021-12-20 0:07 ` Scheme+ Jacob Hrbek
2021-12-20 0:16 ` Scheme+ Damien Mattei
2021-12-20 1:53 ` Scheme+ Jacob Hrbek
2021-12-20 7:22 ` Scheme+ Dr. Arne Babenhauserheide
2021-12-20 8:15 ` Scheme+ Linus Björnstam
2021-12-20 9:20 ` Scheme+ Damien Mattei
2021-12-20 17:33 ` Maxime Devos [this message]
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=7706b14ef6319e7784ee73a74ec399db28751c53.camel@telenet.be \
--to=maximedevos@telenet.be \
--cc=damien.mattei@gmail.com \
--cc=guile-devel@gnu.org \
--cc=guile-user@gnu.org \
--cc=linus.internet@fastmail.se \
/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).