caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sivaramakrishnan KC <kcsrk@iitm.ac.in>
To: "David MENTRÉ" <David.MENTRE@bentobako.org>
Cc: <caml-list@inria.fr>
Subject: Re: [Caml-list] General description of Multicore OCaml?
Date: Wed, 5 Feb 2020 13:10:14 +0530	[thread overview]
Message-ID: <CACVN0Vtw4VAE-d+Vco6uG9maz3o35JoUD884vXyrmgF-fB=57g@mail.gmail.com> (raw)
In-Reply-To: <8e8cfb62-d21d-c4fa-701d-68aa06bad623@bentobako.org>

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

There is a work-in-progress RWO style chapter for Multicore OCaml
programming. This should come alive in the next few weeks. In the meantime,
you can look at the Multicore OCaml section at
https://ocamlverse.github.io/content/future_ocaml.html.

Kind Regards
KC

On Wed, Feb 5, 2020 at 12:43 PM David MENTRÉ <David.MENTRE@bentobako.org>
wrote:

> Hello,
>
> Le 04/02/2020 à 09:47, Alan Schmitt a écrit :
>
> Multicore OCaml: January 2020 update
>
> Archive:
> https://discuss.ocaml.org/t/multicore-ocaml-january-2020-update/5090/1
> Anil Madhavapeddy announced
>
> Is there a blog post or similar that gives a high level view of the
> technical aspects of Multicore OCaml effort? What kind of API will be
> available for OCaml developers? What are the challenges and how are they
> solved?
>
> Best regards,
> D. Mentré
>
>
>

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

  reply	other threads:[~2020-02-05  8:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04  8:47 [Caml-list] Attn: Development Editor, Latest OCaml Weekly News Alan Schmitt
2020-02-05  7:12 ` [Caml-list] General description of Multicore OCaml? David MENTRÉ
2020-02-05  7:40   ` Sivaramakrishnan KC [this message]
2020-02-08 10:27     ` David MENTRÉ

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='CACVN0Vtw4VAE-d+Vco6uG9maz3o35JoUD884vXyrmgF-fB=57g@mail.gmail.com' \
    --to=kcsrk@iitm.ac.in \
    --cc=David.MENTRE@bentobako.org \
    --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).