From: Chris Vine <vine35792468@gmail.com>
To: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: Guile fibers return values
Date: Mon, 6 Jan 2020 21:14:56 +0000 [thread overview]
Message-ID: <20200106211456.68c8a637631a4e1e977d8443@gmail.com> (raw)
In-Reply-To: <7661b27f-787e-fc8f-d653-5fbabffa01f7@posteo.de>
On Mon, 6 Jan 2020 20:42:17 +0100
Zelphir Kaltstahl <zelphirkaltstahl@posteo.de> wrote:
[snip]
> In Racket the futures have some limitations, where one needs to use a
> different number type to enable them in some cases to run in parallel –
> wait, I am looking for the link … here:
> https://docs.racket-lang.org/guide/parallelism.html – Is there any
> similar restriction for futures in Guile?
I don't know. I should try it and see.
next prev parent reply other threads:[~2020-01-06 21:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 1:30 Guile fibers return values Zelphir Kaltstahl
2020-01-05 12:33 ` Chris Vine
2020-01-05 12:58 ` Zelphir Kaltstahl
2020-01-05 14:28 ` Chris Vine
[not found] ` <20200105142358.4ad96d15a23a0b947b2d55e3@gmail.com>
2020-01-05 18:22 ` Zelphir Kaltstahl
2020-01-05 21:45 ` Chris Vine
2020-01-06 19:42 ` Zelphir Kaltstahl
2020-01-06 21:14 ` Chris Vine [this message]
2020-01-06 21:47 ` John Cowan
2020-01-06 22:45 ` Zelphir Kaltstahl
2020-01-07 1:36 ` John Cowan
-- strict thread matches above, loose matches on Subject: below --
2020-01-04 22:49 Zelphir Kaltstahl
2020-01-05 2:42 ` John Cowan
2020-01-05 12:46 ` Zelphir Kaltstahl
2020-01-14 10:59 ` Amirouche Boubekki
2020-01-15 0:04 ` Zelphir Kaltstahl
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=20200106211456.68c8a637631a4e1e977d8443@gmail.com \
--to=vine35792468@gmail.com \
--cc=guile-user@gnu.org \
--cc=zelphirkaltstahl@posteo.de \
/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).