From: Chris King <colanderman@gmail.com>
To: Michal Moskal <michal.moskal@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Shallow copy of a record
Date: Sat, 22 Jan 2005 15:08:40 -0500 [thread overview]
Message-ID: <875c7e0705012212084b02b76e@mail.gmail.com> (raw)
In-Reply-To: <b323bb980501220955551e3e63@mail.gmail.com>
On Sat, 22 Jan 2005 18:55:40 +0100, Michal Moskal
<michal.moskal@gmail.com> wrote:
> No, consider:
>
> let copy foo = {foo with a = b}
>
> and now, if there were no assign:
>
> let copy foo = {foo}
>
> what should be the type of copy?
Ah okay, I didn't think about that. But I suppose in cases like that,
the type could be forced, as in "let copy foo = { (foo:bar) }".
next prev parent reply other threads:[~2005-01-22 20:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-22 4:27 Chris King
2005-01-22 6:49 ` [Caml-list] " Jacques Garrigue
2005-01-22 16:55 ` Chris King
2005-01-22 17:55 ` Michal Moskal
2005-01-22 20:08 ` Chris King [this message]
2005-01-22 14:17 ` Kurt Welgehausen
2005-01-22 16:45 ` Chris King
[not found] ` <200501221059.28064.jon@jdh30.plus.com>
2005-01-22 17:03 ` Chris King
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=875c7e0705012212084b02b76e@mail.gmail.com \
--to=colanderman@gmail.com \
--cc=caml-list@inria.fr \
--cc=michal.moskal@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).