caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Christophe Raffalli <christophe@raffalli.eu>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] serialization of closures
Date: Fri, 4 Jun 2021 19:14:39 +0200	[thread overview]
Message-ID: <CAH=h3gFgmPXLPMbuLn1De_F8oNyS+ohfiHoUpJk6jL6A+HNU=g@mail.gmail.com> (raw)
In-Reply-To: <20210603171753.nci6b45fepzyupnm@oulala>

[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]

On Thu, Jun 3, 2021 at 7:18 PM Christophe Raffalli <christophe@raffalli.eu>
wrote:

>
> 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 ?
>

I was not aware of this limitation of Multicore OCaml, and looking at its
git history, it looks like it was introduced very early in the development,
perhaps to make things simpler initially.

Marshalling of function closures has always been sort of experimental and
not super reliable, but I was not expecting it to be incompatible with
Multicore OCaml.  We (the core dev team) will sort it out.

Kind regards,

- Xavier Leroy


> Remark: Closures is not marked as obsolete in Marshal.mli
>
> Cheers,
> Christophe
>

[-- Attachment #2: Type: text/html, Size: 1648 bytes --]

      parent reply	other threads:[~2021-06-04 17:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-03 17:17 Christophe Raffalli
2021-06-03 17:20 ` Basile Starynkevitch
2021-06-04 17:14 ` Xavier Leroy [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH=h3gFgmPXLPMbuLn1De_F8oNyS+ohfiHoUpJk6jL6A+HNU=g@mail.gmail.com' \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=christophe@raffalli.eu \
    /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).