From: Christophe Raffalli <christophe@raffalli.eu>
To: caml-list@inria.fr
Subject: [Caml-list] serialization of closures
Date: Thu, 3 Jun 2021 08:17:53 -0900 [thread overview]
Message-ID: <20210603171753.nci6b45fepzyupnm@oulala> (raw)
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
Hello dear camlers,
I just noticed that in 4.12+effect, in the road to multicore, we have now the
nice exception:
Failure("Serializing closures is broken in multicore")
This is a bit a pity: if you want to use both multicore and multi-machine
parallelism, then, marshalling closures was useful for communication between
machines in some cases. Is it a final decision or serialization of closures will
be lost forever in OCaml ?
Remark: Closures is not marked as obsolete in Marshal.mli
Cheers,
Christophe
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2021-06-03 17:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 17:17 Christophe Raffalli [this message]
2021-06-03 17:20 ` Basile Starynkevitch
2021-06-04 17:14 ` Xavier Leroy
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210603171753.nci6b45fepzyupnm@oulala \
--to=christophe@raffalli.eu \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).