From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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 E8F9DE709A for ; Tue, 17 Nov 2020 07:38:32 +0100 (CET) X-IronPort-AV: E=Sophos;i="5.77,484,1596492000"; d="scan'208";a="364746739" Received: from 91-175-127-215.subs.proxad.net (HELO MacBook-Pro-5.local) ([91.175.127.215]) by mail3-relais-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Nov 2020 07:38:32 +0100 Cc: Mailing List OCaml References: <9F66A427-C0B7-44B6-AE07-330D031FD631@gmail.com> From: =?UTF-8?Q?Fran=c3=a7ois_Pottier?= Message-ID: <11d5773c-bb41-6279-4d7a-b208dcb0350e@inria.fr> Date: Tue, 17 Nov 2020 07:38:31 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.1 MIME-Version: 1.0 In-Reply-To: <9F66A427-C0B7-44B6-AE07-330D031FD631@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: fr Content-Transfer-Encoding: 8bit Subject: Re: [Caml-list] Lack of an empty variant type Le 17/11/2020 à 02:02, Jacques Garrigue a écrit : > Can’t you work around that by adding a dummy element to your sets? Hi Jacques, yes, I can; but it adds visual clutter to types that are already difficult to read. Not a big deal, I guess. -- François Pottier francois.pottier@inria.fr http://cambium.inria.fr/~fpottier/