caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Yaron Minsky <yminsky@janestreet.com>,
	OCaML List Mailing <caml-list@inria.fr>,
	 Jacques Carette <carette@mcmaster.ca>
Subject: Re: [Caml-list] Record field disambiguation in 4.01
Date: Wed, 13 Mar 2013 05:42:38 +0900	[thread overview]
Message-ID: <CA+p7B-wPJuP5DoMVNsn=TMHZDss47o+qm-YCHE=n4AD3LMcaGg@mail.gmail.com> (raw)
In-Reply-To: <CAPFanBFqR06W6nLeQSDrS8AtKmmgjKGurMjw8-rejLHRUdNT7w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

It's just that when you look up the label you get a list in reverse order:
last one first.
Would it be really clearer to reverse it at again when printing?

Jacques
2013/03/13 2:08 "Gabriel Scherer" <gabriel.scherer@gmail.com>:

> Also on the new warning (thanks for the quick change!): I find it a
> bit strange that the message gives a list of possibilities then says
> "The first one was selected", while in my mental model the *last*
> declared type is chosen by default. I don't know if it's actually
> possible to list types by declaration order (levels?), but maybe you
> could at least arrange so that the selected one appears last? Or at
> least you could reword into "The last declaration of this field has
> type M.t, but types M.u and N.t would also be valid".
>
> On Tue, Mar 12, 2013 at 4:29 PM, Jacques Carette <carette@mcmaster.ca>
> wrote:
> > On 13-03-12 11:05 AM, Jacques Garrigue wrote:
> >>
> >> I have improved the warning (revision 13395), so that it tells you the
> >> types involved. This should actually help in some hairy situations.
> >
> >
> > Would it also make sense to give the fully qualified names for the
> ambiguous
> > fields?  This should also give a strong hint as to where the conflict
> comes
> > from.
> >
> > (another)  Jacques
> >
> >
> >
> > --
> > 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
>

[-- Attachment #2: Type: text/html, Size: 2224 bytes --]

      reply	other threads:[~2013-03-12 20:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 23:39 Yaron Minsky
2013-03-10  1:24 ` Jacques Garrigue
2013-03-11 11:38   ` Maxence Guesdon
2013-03-12  7:57     ` Alain Frisch
2013-03-10  3:04 ` Markus Mottl
2013-03-10  9:33   ` Gabriel Scherer
2013-03-11 10:31     ` Goswin von Brederlow
2013-03-12 11:30       ` Leo White
2013-03-11 18:49   ` Yaron Minsky
2013-03-11 11:52 ` Alain Frisch
2013-03-11 18:52   ` Yaron Minsky
2013-03-12  8:05     ` Alain Frisch
2013-03-12 15:05     ` Jacques Garrigue
2013-03-12 15:29       ` Jacques Carette
2013-03-12 17:07         ` Gabriel Scherer
2013-03-12 20:42           ` Jacques Garrigue [this message]

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='CA+p7B-wPJuP5DoMVNsn=TMHZDss47o+qm-YCHE=n4AD3LMcaGg@mail.gmail.com' \
    --to=garrigue@math.nagoya-u.ac.jp \
    --cc=caml-list@inria.fr \
    --cc=carette@mcmaster.ca \
    --cc=gabriel.scherer@gmail.com \
    --cc=yminsky@janestreet.com \
    /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).