From: Bob Zhang <bobzhang1988@gmail.com>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Robust left to right flow for record disambiguation
Date: Wed, 23 Oct 2013 23:11:39 -0400 [thread overview]
Message-ID: <CANcqPu6f0Fk+9Rqke3pi7brRw50nKDtcE7ez+Qwz5ZR459vMag@mail.gmail.com> (raw)
In-Reply-To: <C34DDC63-35B3-43EA-8361-13160A4A849E@math.nagoya-u.ac.jp>
Hi Jacques,
> Case 2 seems more reasonable (after replacing (u:t) by (u:u)).
> In particular,
> let f (u:u) =
> match u with `Key loc -> loc.loc
> already works, so it seems strange that the pattern-matching version doesn't.
Sorry for the typo
I expected
let f (u:u) = match u with `Key {loc} -> loc
to work, it does not yet (against 4.01.0)
>
> Jacques
--
Regards
-- Bob
next prev parent reply other threads:[~2013-10-24 3:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-23 20:52 Bob Zhang
2013-10-24 1:40 ` Jacques Garrigue
2013-10-24 3:11 ` Bob Zhang [this message]
2013-10-25 9:20 ` Alain Frisch
2013-10-25 11:27 ` Didier Remy
2013-10-25 12:39 ` Alain Frisch
2013-10-25 13:06 ` Wojciech Meyer
2013-10-26 6:05 ` oleg
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=CANcqPu6f0Fk+9Rqke3pi7brRw50nKDtcE7ez+Qwz5ZR459vMag@mail.gmail.com \
--to=bobzhang1988@gmail.com \
--cc=caml-list@inria.fr \
--cc=garrigue@math.nagoya-u.ac.jp \
/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).