From: Josh Berdine <josh@berdine.net>
To: ygrek <ygrek@autistici.org>, caml-list@inria.fr
Subject: Re: [Caml-list] They have different arities
Date: Tue, 04 Jul 2017 10:15:06 +0100 [thread overview]
Message-ID: <jk60igvan8o95x.fsf@fb.com> (raw)
In-Reply-To: <20170704012122.71fe4a55@kiwi.local.tld>
On Tue, Jul 04 2017, ygrek wrote:
> Consider the following :
> ```
> # type t' = int option;;
> type t' = int option
> # type t = int option = None | Some of int;;
> Characters 0-40:
> type t = int option = None | Some of int;;
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Error: This variant or record definition does not match that of type
> int option
> They have different arities.
> ```
As a workaround, is it feasible for you to do the re-export and instantiation in separate steps?
```
type 'a t' = 'a option = None | Some of 'a
type t = int t'
```
next prev parent reply other threads:[~2017-07-04 9:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 8:21 ygrek
2017-07-04 9:15 ` Josh Berdine [this message]
2017-07-06 5:50 ` ygrek
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=jk60igvan8o95x.fsf@fb.com \
--to=josh@berdine.net \
--cc=caml-list@inria.fr \
--cc=ygrek@autistici.org \
/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).