caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Nils Becker <nils.becker@bioquant.uni-heidelberg.de>
To: caml-list@inria.fr
Subject: [Caml-list] pattern matching on mapped lists
Date: Wed, 03 Jun 2015 00:23:29 +0200	[thread overview]
Message-ID: <556E2CE1.9040801@bioquant.uni-heidelberg.de> (raw)
In-Reply-To: <20150602100015.E87D67EEF7@sympa.inria.fr>

I find this syntax handy

    let [ii; jj] = List.map float_of_int [i; j] in
    ... do stuff with the floats

because it avoids repeating the function call. The compiler lets this
pass but warns that the matching is not exhaustive since [] is not
matched. This actually can't happen if I'm not mistaken. So, is this
considered good style, or is there a better idiomatic way to do multiple
assignments? If yes, should this be an enhancement request for the type
checker?

n.



       reply	other threads:[~2015-06-02 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150602100015.E87D67EEF7@sympa.inria.fr>
2015-06-02 22:23 ` Nils Becker [this message]
2015-06-03 16:52   ` Romain Bardou
2015-06-03 17:42     ` Mikhail Mandrykin
2015-06-03 18:06       ` Octachron
2015-06-03 16:58   ` John Whitington

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=556E2CE1.9040801@bioquant.uni-heidelberg.de \
    --to=nils.becker@bioquant.uni-heidelberg.de \
    --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).