From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id C8D977EE25 for ; Fri, 1 Nov 2013 16:49:31 +0100 (CET) X-IronPort-AV: E=Sophos;i="4.93,618,1378850400"; d="scan'208";a="33065021" Received: from cac94-1-81-57-150-173.fbx.proxad.net (HELO [192.168.0.22]) ([81.57.150.173]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/AES128-SHA; 01 Nov 2013 16:49:31 +0100 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v1283) From: Damien Doligez In-Reply-To: Date: Fri, 1 Nov 2013 16:49:30 +0100 Content-Transfer-Encoding: 7bit Message-Id: <41ECAD85-CC65-41A5-AD6E-21F4B85C932D@inria.fr> References: <1383167277.75943.YahooMailNeo@web120402.mail.ne1.yahoo.com> To: caml users X-Mailer: Apple Mail (2.1283) Subject: Re: [Caml-list] Operator for Lazy.force? 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