From: Michael Ekstrand <michael@elehack.net>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Option functions (or lack thereof) + operator for composition
Date: Tue, 16 Nov 2010 08:26:41 -0600 [thread overview]
Message-ID: <4CE294A1.5050100@elehack.net> (raw)
In-Reply-To: <AANLkTimX1JOva2Ebc3FuTGiZ5W3zXAvHtoE9RrkO8v6=@mail.gmail.com>
On 11/16/2010 05:27 AM, Serge Le Huitouze wrote:
> 2. Operator for composition (and its precedence)
> ********************************************************
> To get rid of many warnings, I wrapped some calls (the "connect" calls of
> my widgets) into "ignore (f x y)" statements.
> I've no particular grief in using "ignore", but I find the parentheses
> *really* annoying.
>
> In Haskell, I would write "ignore $ f x y", which I find much lighter weight.
>
> I'm not familiar with operators and their precedence, but I wonder: is it
> possible to do something similar with OCaml?
Batteries provides operators for things like this. It defines the '**>'
operator for function application; it's an odd name, but it has the
right associativity. As Dmitry mentioned, some override (&). Batteries
also provides composition operators |- and -|, and a pipeline operator
|> (opposite of **>). With that operator, you can write:
f x y |> ignore
thereby putting the emphasis on "f x y" and relegating "ignore" to a
cleanup at the end.
- Michael
next prev parent reply other threads:[~2010-11-16 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 11:27 Serge Le Huitouze
2010-11-16 11:49 ` [Caml-list] " David Allsopp
2010-11-16 14:23 ` Michael Ekstrand
2010-11-16 13:30 ` Jacques Garrigue
2010-11-16 13:52 ` Serge Le Huitouze
2010-11-16 14:19 ` dmitry grebeniuk
2010-11-16 14:26 ` Michael Ekstrand [this message]
2010-11-16 15:18 ` bluestorm
2010-11-16 15:26 ` bluestorm
[not found] <1853021343.44703.1289906871683.JavaMail.root@zmbs4.inria.fr>
2010-11-16 11:43 ` Thomas Gazagnaire
2010-11-16 11:51 ` Gabriel Kerneis
2010-11-16 17:45 ` Martin Jambon
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=4CE294A1.5050100@elehack.net \
--to=michael@elehack.net \
--cc=caml-list@yquem.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