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 AAF4E7F7AF for ; Sat, 10 Oct 2015 16:11:59 +0200 (CEST) IronPort-PHdr: 9a23:OZ6cdhXK/cDnjTu7ngPHYjqsj17V8LGtZVwlr6E/grcLSJyIuqrYZheFt8tkgFKBZ4jH8fUM07OQ6PC8HzNRqsjQ+Fk5M7VyFDY9wf0MmAIhBMPXQWbaF9XNKxIAIcJZSVV+9Gu6O0UGUOz3ZlnVv2HgpWVKQka3CwN5K6zPF5LIiIzvjqbpq8GVPFQD2mv1SIgxBSv1hD2ZjtMRj4pmJ/R54TryiVwMRd5rw3h1L0mYhRf265T41pdi9yNNp6BprJYYAu2pN5g/GLdRCTBjN2Eu+OXqswPCRE2B/CgySGITxx1DHwHO7Av9WN+ltSDmv8Jl3y2LNs3xV7cyHzq4ufQ4ACT0gTsKYmZquFrcjdZ92fpW Authentication-Results: mail3-smtp-sop.national.inria.fr; spf=None smtp.pra=octa@polychoron.fr; spf=None smtp.mailfrom=octa@polychoron.fr; spf=None smtp.helo=postmaster@relay6-d.mail.gandi.net Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of octa@polychoron.fr) identity=pra; client-ip=217.70.183.198; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="octa@polychoron.fr"; x-sender="octa@polychoron.fr"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of octa@polychoron.fr) identity=mailfrom; client-ip=217.70.183.198; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="octa@polychoron.fr"; x-sender="octa@polychoron.fr"; x-conformance=sidf_compatible Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@relay6-d.mail.gandi.net) identity=helo; client-ip=217.70.183.198; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="octa@polychoron.fr"; x-sender="postmaster@relay6-d.mail.gandi.net"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: A0A9AgB4HBlWlMa3RtlehG6nUIE1BpRlgVqDEzKBWH8CgSA5EwEBAQEBAQEBEAEBAQEHDQkJIS6CH4IIAQEEIwQLAQVAEQsaAgUWCwICCQMCAQIBRRMIAQGIKAYDr16TfSyBIoUKhUWFFBeCUoFFBY0NiQaBUpRbkm4CIwOCZIFdh1OBBgEBAQ X-IPAS-Result: A0A9AgB4HBlWlMa3RtlehG6nUIE1BpRlgVqDEzKBWH8CgSA5EwEBAQEBAQEBEAEBAQEHDQkJIS6CH4IIAQEEIwQLAQVAEQsaAgUWCwICCQMCAQIBRRMIAQGIKAYDr16TfSyBIoUKhUWFFBeCUoFFBY0NiQaBUpRbkm4CIwOCZIFdh1OBBgEBAQ X-IronPort-AV: E=Sophos;i="5.17,663,1437429600"; d="scan'208";a="150158803" Received: from relay6-d.mail.gandi.net ([217.70.183.198]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 10 Oct 2015 16:11:40 +0200 Received: from mfilter21-d.gandi.net (mfilter21-d.gandi.net [217.70.178.149]) by relay6-d.mail.gandi.net (Postfix) with ESMTP id E634E4F1CC7 for ; Sat, 10 Oct 2015 16:11:39 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mfilter21-d.gandi.net Received: from relay6-d.mail.gandi.net ([IPv6:::ffff:217.70.183.198]) by mfilter21-d.gandi.net (mfilter21-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id lk3ZwZKtcWUd for ; Sat, 10 Oct 2015 16:11:38 +0200 (CEST) X-Originating-IP: 197.88.12.131 Received: from [192.168.1.104] (unknown [197.88.12.131]) (Authenticated sender: octa@polychoron.fr) by relay6-d.mail.gandi.net (Postfix) with ESMTPSA id 0BE234F1AE4 for ; Sat, 10 Oct 2015 16:11:37 +0200 (CEST) To: caml-list@inria.fr References: From: octachron Message-ID: <56191C97.5000003@polychoron.fr> Date: Sat, 10 Oct 2015 16:11:35 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [Caml-list] pipe input short syntax idea Hi, If you just want a short notation for (fun x -> x |> f |> g |> ...), why not simply define a composition operator? With let (->-) f g x = x |> f |> g;; you can rewrite the previous expression as f ->- g ->- h ... I personally don't think that there is any need for a special syntax here. At the same time, it could be nice if there was a standardized name for composition operators. —octachron. Le 10/10/15 15:52, Nils Becker a écrit : > hi, > > just an idea for a short notation which might be appealing: > > (|> f |> g |> ... ) as abbreviation for (fun x -> x |> f |> g |> ...) > > (|> f) would be just f. > > in other words a it's function composition using |> . it looks intuitive > to me. but of course it could be a bad idea for a lot of reasons. > > n, > >