From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2-relais-roc.national.inria.fr (mail2-relais-roc.national.inria.fr [192.134.164.83]) by sympa.inria.fr (Postfix) with ESMTPS id ED3C67EE99 for ; Mon, 20 Jan 2014 12:23:12 +0100 (CET) X-IronPort-AV: E=Sophos;i="4.95,689,1384297200"; d="scan'208";a="53996132" Received: from sympa.inria.fr ([193.51.193.213]) by mail2-relais-roc.national.inria.fr with ESMTP; 20 Jan 2014 12:23:12 +0100 Received: by sympa.inria.fr (Postfix, from userid 20132) id E2DE57F6C4; Mon, 20 Jan 2014 12:23:12 +0100 (CET) Date: Mon, 20 Jan 2014 12:23:08 +0100 To: caml-list@inria.fr In-Reply-To: <20140120101654.GI26447@frosties> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7BIT From: "Jonathan Kimmitt" X-Mailer: Sympa 6.1.17 Subject: Re: [Caml-list] How much optimized is the 'a option type ? OCaml already uses the number 1 to represent 0(sic), [], and None. Type safety prevents them getting mixed up. The integer 1 would be represented by 3, and so on. Since pointers are always even (on sensible platforms) this helps the garbage collector to quickly scan without caring too much about what it all means.