From: Damien Doligez <damien.doligez@inria.fr>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Operator for Lazy.force?
Date: Fri, 1 Nov 2013 16:49:30 +0100 [thread overview]
Message-ID: <41ECAD85-CC65-41A5-AD6E-21F4B85C932D@inria.fr> (raw)
In-Reply-To: <CAPi0vKXA+80vOn6e1C7en=2rfMUsYjEtp_kF=0=3Y1V26sY8+Q@mail.gmail.com>
Hello,
On 2013-10-30, at 22:33, Dmitry Grebeniuk wrote:
> So theirs ( !! ) operator will override Pervasives' one.
> What's the problem? Anyway projects you've mentioned don't use Lazy,
> so there's no chance of "operator clash".
It cannot be in Pervasives, since that would introduce a circular
dependency with Lazy. It doesn't belong in Pervasives anyway.
The best you can do is define it in a submodule of Lazy, for example
Lazy.Op, and let the user do
open Lazy.Op;;
to access the operator without too much verbosity.
-- Damien
next prev parent reply other threads:[~2013-11-01 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 18:51 Lukasz Stafiniak
2013-10-30 21:07 ` Dario Teixeira
2013-10-30 21:33 ` Dmitry Grebeniuk
2013-10-31 11:10 ` Dario Teixeira
2013-11-01 15:49 ` Damien Doligez [this message]
2013-11-02 19:03 ` David Allsopp
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=41ECAD85-CC65-41A5-AD6E-21F4B85C932D@inria.fr \
--to=damien.doligez@inria.fr \
--cc=caml-list@inria.fr \
/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).