From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id D06F97FE36 for ; Fri, 1 Jul 2016 02:41:56 +0200 (CEST) IronPort-PHdr: 9a23:XruTWBRdvqTQNnRAvgrlfILSs9psv+yvbD5Q0YIujvd0So/mwa64ZxeN2/xhgRfzUJnB7Loc0qyN4vimADxLus3JmUtBWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnYsExnyfTB4Ov7yUtaLyZ/mj6brq9aIOE1hv3mUWftKNhK4rAHc5IE9oLBJDeIP8CbPuWZCYO9MxGlldhq5lhf44dqsrtY4q3wD86Fpy8kVWqz/e+E8TKdEJDUgKWE8osPx5jfZSg7axnYaXn8XkVJiBA/ApEX6U5H9qCr5nvZ6wC6be9XxSqlyUjOnufQ4ACT0gTsKYmZquFrcjdZ92fpW Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=hendrik@topoi.pooq.com; spf=None smtp.mailfrom=hendrik@topoi.pooq.com; spf=None smtp.helo=postmaster@april.topoi.pooq.com Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of hendrik@topoi.pooq.com) identity=pra; client-ip=69.165.131.134; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="hendrik@topoi.pooq.com"; x-sender="hendrik@topoi.pooq.com"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of hendrik@topoi.pooq.com) identity=mailfrom; client-ip=69.165.131.134; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="hendrik@topoi.pooq.com"; x-sender="hendrik@topoi.pooq.com"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@april.topoi.pooq.com) identity=helo; client-ip=69.165.131.134; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="hendrik@topoi.pooq.com"; x-sender="postmaster@april.topoi.pooq.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CgEQAku3VX/4aDpUVbhBRLAYMnuFgehXkCgXERAQEBAQEBAQFkJ0EQAYFgghsBAQQ6TyMJJQ8FGFgHiBUOxCABAQEHAgEfBZACgmCCLwWZC4ExhFeILwpmjkSQBTQggggcgWgggguHaAEBAQ X-IPAS-Result: A0CgEQAku3VX/4aDpUVbhBRLAYMnuFgehXkCgXERAQEBAQEBAQFkJ0EQAYFgghsBAQQ6TyMJJQ8FGFgHiBUOxCABAQEHAgEfBZACgmCCLwWZC4ExhFeILwpmjkSQBTQggggcgWgggguHaAEBAQ X-IronPort-AV: E=Sophos;i="5.26,554,1459807200"; d="scan'208";a="183391502" Received: from topoi.pooq.com (HELO april.topoi.pooq.com) ([69.165.131.134]) by mail3-smtp-sop.national.inria.fr with ESMTP; 01 Jul 2016 02:41:54 +0200 Received: by april.topoi.pooq.com (Postfix, from userid 1001) id 911B6C20CE; Thu, 30 Jun 2016 20:41:52 -0400 (EDT) Date: Thu, 30 Jun 2016 20:41:52 -0400 From: Hendrik Boom To: caml-list@inria.fr Message-ID: <20160701004152.GA23017@topoi.pooq.com> References: <7785E51D-EC74-4A78-8840-D4A7C18E3C56@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Subject: [Caml-list] Async and lwt On Thu, Jun 30, 2016 at 08:13:58PM -0400, Yaron Minsky wrote: > I'm not at all sure that the decoupling is possible or wise for Async. > My intuition is that this is too complex of a problem with too much > need for careful optimization to be able to have a simple, shared > generic data structure for this. > > The solution that seems most plausible to me is to settle on one > implementation, and port the API of one library to run on top of the > other. There was indeed an experiment in this direction that was done > by Jeremie Dimino: > > https://github.com/janestreet/lwt-async > > That said, until we resolve the binary size issues with Core and > therefore Async, I doubt that this solution would be appealing to the > full community of lwt users. What are the conceptual differences between Async and lwt? Does either of them manage to take advantage of a shared-heap multicore system? -- hendrik