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 mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id 5BB707FE36 for ; Fri, 1 Jul 2016 02:14:03 +0200 (CEST) IronPort-PHdr: 9a23:JqHFHReU7g4KI5J2EuD1yw/PlGMj4u6mDksu8pMizoh2WeGdxc6yYh7h7PlgxGXEQZ/co6odzbGH6+a5CSdbut6oizMrSNR0TRgLiMEbzUQLIfWuLgnFFsPsdDEwB89YVVVorDmROElRH9viNRWJ+iXhpQAbFhi3DwdpPOO9QteU1JXvkbnisMaIKyxzxxOFKYtoKxu3qQiD/uI3uqBFbpgL9x3Sv3FTcP5Xz247bXianhL7+9vitMU7q3cYk7sb+sVBSaT3ebgjBfwdVWx+cjMD39DwrRTIUSeI43IdVC1WzksJUED560TbQJ73+gT9qu1j0ymbIda+GbEqVhyj4qpmDhjyh3FUGSQ+9TTmg9Z3iup+oRS6pA03l5/RYYeON+tWfKrbcMgGX2dMQoBaUCkXUdD0VJcGE+dUZbUQlIL6vVZb6EbnCA== Authentication-Results: mail2-smtp-roc.national.inria.fr; spf=None smtp.pra=yminsky@janestreet.com; spf=Pass smtp.mailfrom=yminsky@janestreet.com; spf=None smtp.helo=postmaster@mxout3.mail.janestreet.com Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of yminsky@janestreet.com) identity=pra; client-ip=38.105.200.229; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yminsky@janestreet.com"; x-sender="yminsky@janestreet.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail2-smtp-roc.national.inria.fr: domain of yminsky@janestreet.com designates 38.105.200.229 as permitted sender) identity=mailfrom; client-ip=38.105.200.229; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yminsky@janestreet.com"; x-sender="yminsky@janestreet.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail2-smtp-roc.national.inria.fr: no sender authenticity information available from domain of postmaster@mxout3.mail.janestreet.com) identity=helo; client-ip=38.105.200.229; receiver=mail2-smtp-roc.national.inria.fr; envelope-from="yminsky@janestreet.com"; x-sender="postmaster@mxout3.mail.janestreet.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0CPAQDstHVXfeXIaSZbhBR9BqgehR2OCyKFdQKBLQc8EAEBAQEBAQEBEQEBCRYJUIIyghsBAQQSER0BASwLAQ8LCwMKAgIJHQICIQESAQUBChIGExICBweHdAMXAwumJ4ExPjGKVGeEQwEBBYcoAwqEGwEBAQEBAQEBAgEBAQEBAQEBFwgQcYUnhE6CQ4FjgxuCWoZVDIckilc0hgiGLoILgjiMcogThjMSHoEPNYInHIFoUolBAQEB X-IPAS-Result: A0CPAQDstHVXfeXIaSZbhBR9BqgehR2OCyKFdQKBLQc8EAEBAQEBAQEBEQEBCRYJUIIyghsBAQQSER0BASwLAQ8LCwMKAgIJHQICIQESAQUBChIGExICBweHdAMXAwumJ4ExPjGKVGeEQwEBBYcoAwqEGwEBAQEBAQEBAgEBAQEBAQEBFwgQcYUnhE6CQ4FjgxuCWoZVDIckilc0hgiGLoILgjiMcogThjMSHoEPNYInHIFoUolBAQEB X-IronPort-AV: E=Sophos;i="5.26,554,1459807200"; d="scan'208";a="224971638" Received: from mxout3.mail.janestreet.com ([38.105.200.229]) by mail2-smtp-roc.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Jul 2016 02:14:02 +0200 Received: from tot-qpr-mailcore1.delacy.com ([172.27.56.68] helo=tot-qpr-mailcore1) by mxout3.mail.janestreet.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from ) id 1bIm5o-0006Uj-0J for caml-list@inria.fr; Thu, 30 Jun 2016 20:14:00 -0400 X-JS-Flow: external X-JS-Scanner-attachment: (ok) No attachments Received: by tot-qpr-mailcore1 with JS-mailcore (0.1) (envelope-from ) id BXdbXH-AAAD4X-eT; 2016-06-30 20:13:59.971641-04:00 Received: from mail-vk0-f72.google.com ([209.85.213.72]) by mxgoog1.mail.janestreet.com with esmtps (UNKNOWN:AES128-GCM-SHA256:128) (Exim 4.72) (envelope-from ) id 1bIm5n-0007vG-SZ for caml-list@inria.fr; Thu, 30 Jun 2016 20:13:59 -0400 Received: by mail-vk0-f72.google.com with SMTP id j65so23360943vkg.3 for ; Thu, 30 Jun 2016 17:13:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=janestreet.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JmSz9YYJhnoO+9b8Z2U9zIGod5MJS4f8XxjUoPNEPZA=; b=jhDkKMojYehYhmAX2lcCZkEc7v5dOH7hOo4BPjNsbVVsMkresExFBT02nYtjXEIj1A 9DXkujXGydgREkVfgLx/I+SSo1+yVJ0oY2ET7/A1UxkJa9J7h9QGSclXqqm0C54nlMti K/Puri1RrP8iyUVv/H5jOCVzurT9LvrV1DtTY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JmSz9YYJhnoO+9b8Z2U9zIGod5MJS4f8XxjUoPNEPZA=; b=OAZv0hYhjVTdwIDTf0RW88zarUi/Qd920doX6jALEA03ZDCg0NfRYIxyofxf5rm+gs e/tgVuSe1MJphar/Ck//SsAVKnQwv+hvD6MD4XuEUTwWKlDFfrogwKXfIV4A5nRSbWCH 2D+zBXElXcVB4mnaIBFUEwG/xCqV2B1zmr103QVQEBq2dvlJlDsK9iJsPEljNG8eBkEh LXIZ0vod9CJGOnz+Rng1ZaPAoU3cvMmdSxKgfIuYlvQFE/auWUvJ+t3JF1bg9XRkP5F1 sDBNXsnEf3/kmJhErEviGtpGMk6q2Cn4t4sbPmfBMpA+DHJdvFNl2oeL6VSxVkuz4S5x YRAA== X-Gm-Message-State: ALyK8tJN2k2UK9nTLPLszqtdv3e+lJ8FI4Erl9UPU+zsOe0fLSFowOKj8YH8KnBAz69SKRBuhVXffXibSIjz9bEyWDCxwkQvAORcSV4/kzzpHVFdYY50JgCuj/pJBSzH5PHsO4WfLFNZj17KZQlsJlLRWlk8wWnQEdRBcuF+NxI= X-Received: by 10.13.254.130 with SMTP id o124mr8137716ywf.30.1467332039530; Thu, 30 Jun 2016 17:13:59 -0700 (PDT) X-Received: by 10.13.254.130 with SMTP id o124mr8137704ywf.30.1467332038767; Thu, 30 Jun 2016 17:13:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.37.52.200 with HTTP; Thu, 30 Jun 2016 17:13:58 -0700 (PDT) In-Reply-To: References: <7785E51D-EC74-4A78-8840-D4A7C18E3C56@gmail.com> From:Yaron Minsky Date: Thu, 30 Jun 2016 20:13:58 -0400 Message-ID: To:Ivan Gotovchits Cc:Dean Thompson , caml-list , Jeremy Yallop Content-Type: text/plain; charset=UTF-8 X-JS-Processed-by: mailcore Subject: Re: [Caml-list] how to encourage adoption of OCaml? 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. y On Thu, Jun 30, 2016 at 9:13 AM, Ivan Gotovchits wrote: > > > On Thu, Jun 30, 2016 at 8:12 AM, Yaron Minsky > wrote: >> >> A few thoughts: >> >> As Anil said, we're working on an updated RWO, which should resolve the >> camlp4 issue. >> >> As for mixing and matching between libraries that do and don't depend on >> Core, there's actually little difficulty here. Core sticks to the standard >> interchange types (array, string, option, list, char, and now result) that >> are provided by the stdlib, so whether you use Core (or Core_kernel) becomes >> more a matter of personal preference, and shouldn't hinder interoperability. >> >> One remaining problem with Core is the minimal executable size, which is >> currently much bigger if you use Core. We're considering some work in three >> next few months to make this much better. >> >> Async and Lwt are a real problem. They provide very similar functionality, >> and mixing and matching between two schedulers is not so easy. I'd love to >> see some resolution here, but it's not clear what the solution would be. > > The solution would be to use the same approach as with standard types. We > need a common base inductive type for `Lwt.t` (aka `Ivar.t`), which will > represent a value which is defined in some point in the future (hence a > `future` is a good name). Another type is for capturing a concept of a > variable that can have multiple values in the future, that is represented as > `Lwt_stream.t` or `Pipe`. Currently in both Lwt and Async the main thread > type is tightly coupled with the underlying implementation, especially in > Async (Lwt.t can be easily decoupled). >> >> y >> >> On Jun 30, 2016 6:32 AM, "Dean Thompson" >> wrote: >>> >>> From my understanding so far, it seems to me that mixing and matching >>> Core and not-Core would be tough? Everything from result types to Lwt vs >>> Async? Given the inspirational and educational power of Real World OCaml, >>> many newcomers will face this issue. >>> >>> Dean >>> >>> >>> > On Jun 30, 2016, at 6:17 AM, Jeremy Yallop wrote: >>> > >>> >> On 30 June 2016 at 11:01, Dean Thompson >>> >> wrote: >>> >> It is hard for me to judge because I came through RWO, but it appears >>> >> to me that the lack of consensus on standard library comes up pretty >>> >> quickly. >>> > >>> > I think the standard library situation is much less of a concern than >>> > it once was, now that it's easy to distribute small OCaml packages and >>> > manage dependencies. >>> > >>> > In the past distribution difficulties discouraged dependencies: for >>> > example, even though many people prefer the design of ocaml-re and >>> > ocaml-pcre to the regular expression facilities in the standard >>> > library, the administrative overhead of an additional dependency made >>> > the standard library the easier choice overall. In that situation >>> > it's desirable for the standard library to be large and featureful. >>> > Nowadays there's much less benefit to having regular expression >>> > support in the standard library, since depending on ocaml-re or >>> > ocaml-pcre is just a matter of adding a line to an opam file and a few >>> > lines to the build configuration. >>> > >>> > The standard library still has a useful role to play, since it's >>> > easier to make libraries interoperate if they can communicate via >>> > common types, and several recent and proposed changes have that kind >>> > of role in mind. For example, the latest release of OCaml added a >>> > 'result' type to the standard library, which was previously defined in >>> > incompatible but essentially equivalent ways in several libraries: >>> > >>> > https://github.com/ocaml/ocaml/pull/147 >>> > >>> > and there's a proposal for adding iterators to various container types >>> > for the next release currently under discussion: >>> > >>> > https://github.com/ocaml/ocaml/pull/635 >>> >>> -- >>> Caml-list mailing list. Subscription management and archives: >>> https://sympa.inria.fr/sympa/arc/caml-list >>> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners >>> Bug reports: http://caml.inria.fr/bin/caml-bugs > >