From: "Stephen Weeks" <sweeks@sweeks.com>
To: "Derek Dreyer" <dreyer.publicity@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] question on type checking
Date: Wed, 21 Mar 2007 21:13:25 -0400 [thread overview]
Message-ID: <604682010703211813j12529ba1h5f4931fe69dcd88f@mail.gmail.com> (raw)
In-Reply-To: <db810ed70703210851o5ca0d4b4ia10da86a57201b79@mail.gmail.com>
Thanks for the reply Derek. I also thought it looked like a bug, and
your explanation makes sense. However, Markus Mottl pointed me to the
following issue in the bug tracker
http://caml.inria.fr/mantis/view.php?id=3476
The problem there looks very similar, and would seem to indicate that
the situation is not viewed as a bug (in the sense that it won't be
fixed).
next prev parent reply other threads:[~2007-03-22 1:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-20 18:20 Stephen Weeks
2007-03-21 15:51 ` [Caml-list] " Derek Dreyer
2007-03-22 1:13 ` Stephen Weeks [this message]
2007-03-22 4:32 ` Derek Dreyer
2007-03-26 14:24 ` Xavier Leroy
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=604682010703211813j12529ba1h5f4931fe69dcd88f@mail.gmail.com \
--to=sweeks@sweeks.com \
--cc=caml-list@yquem.inria.fr \
--cc=dreyer.publicity@gmail.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).