From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.1.3 X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by yquem.inria.fr (Postfix) with ESMTP id EFACCBC69 for ; Wed, 14 Nov 2007 17:39:01 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AgAAADazOkfB/BYflmdsb2JhbACPAwIBAQcEBhERBw X-IronPort-AV: E=Sophos;i="4.21,417,1188770400"; d="scan'208";a="4459411" Received: from smtp20.orange.fr ([193.252.22.31]) by mail1-smtp-roc.national.inria.fr with ESMTP; 14 Nov 2007 17:39:01 +0100 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf2023.orange.fr (SMTP Server) with ESMTP id AAAFA1C0008F for ; Wed, 14 Nov 2007 17:39:01 +0100 (CET) Received: from [192.168.1.59] (APuteaux-154-1-12-161.w83-199.abo.wanadoo.fr [83.199.69.161]) by mwinf2023.orange.fr (SMTP Server) with ESMTP id 8131D1C0008B; Wed, 14 Nov 2007 17:39:01 +0100 (CET) X-ME-UUID: 20071114163901529.8131D1C0008B@mwinf2023.orange.fr Message-ID: <473B249D.9040703@frisch.fr> Date: Wed, 14 Nov 2007 17:38:53 +0100 From: Alain Frisch User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Pierre Weis Cc: caml-list Subject: Re: [Caml-list] Compiler feature - useful or not? References: <473A363F.2080301@gmail.com> <891bd3390711131608g48b584a4n6b0ccab95d7de3f3@mail.gmail.com> <20071114075827.GA24058@yquem.inria.fr> <473AEC04.3030303@frisch.fr> <20071114143524.GA4423@yquem.inria.fr> In-Reply-To: <20071114143524.GA4423@yquem.inria.fr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam: no; 0.00; frisch:01 frisch:01 compiler:01 weis:01 wrote:01 abstract:01 abstract:01 caml-list:01 int:01 int:01 alain:01 alain:01 pierre:02 pattern:04 guess:04 Pierre Weis wrote: > a private type is not an abstract type but a concrete type. I guess I got a wrong intuition of the new feature because of the "from" function in your example. Is it the case that a value of type "abstract int" can always be used as a value of type "int" automatically (you mention that it is ok for pattern matching at least)? -- Alain