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 3DFEE7EE4B for ; Thu, 10 Oct 2013 21:17:31 +0200 (CEST) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of yotambarnoy@gmail.com) identity=pra; client-ip=209.85.216.175; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="yotambarnoy@gmail.com"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of yotambarnoy@gmail.com designates 209.85.216.175 as permitted sender) identity=mailfrom; client-ip=209.85.216.175; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="yotambarnoy@gmail.com"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@mail-qc0-f175.google.com) identity=helo; client-ip=209.85.216.175; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="yotambarnoy@gmail.com"; x-sender="postmaster@mail-qc0-f175.google.com"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AtMBAEz8VlLRVdivm2dsb2JhbABZhBHCSQgWDgEBAQEBBgsLCRQoghw3GQEbHgMSCAECBV0BEQEFASKIBgEDD5h7gwSMVYMKhBUKGScNZIkBAQUMk2UDmAWQFxgphGog X-IPAS-Result: AtMBAEz8VlLRVdivm2dsb2JhbABZhBHCSQgWDgEBAQEBBgsLCRQoghw3GQEbHgMSCAECBV0BEQEFASKIBgEDD5h7gwSMVYMKhBUKGScNZIkBAQUMk2UDmAWQFxgphGog X-IronPort-AV: E=Sophos;i="4.90,1074,1371074400"; d="scan'208";a="29864396" Received: from mail-qc0-f175.google.com ([209.85.216.175]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/RC4-SHA; 10 Oct 2013 21:17:30 +0200 Received: by mail-qc0-f175.google.com with SMTP id v2so2141584qcr.20 for ; Thu, 10 Oct 2013 12:17:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=GTLTMdjqXEd7SJIfljP75JFU9b6HzlVVpHgz6CCN/n8=; b=NWzvGU/LnqXNdozQm0E6abcv0eMOhUGyFW6RiItXwLGYPFXbp2qe/zi5T1WXtRSoci jbtCo8IrbFTtQFCvGQeBjIuU4Ndpyh4UsJ/h5qcfJmOieCHZl0OvKqhXXYDd3IOCCr/j /tLX74pQGVEAEBfTVllmciaFNeCjVtNS4OSbPO5y93nMLVQt89yiWYmNJfvZjAubM1qC oSoglLoRCD1DunJgMv/YpHQhJEPLyZFUKuHVNcffipPI9f2YAYWfcRYqRoOxjqjtQMcJ 6q0WPBv6VlVLUFe66NizVRgANChEvHaE2Y6W9dmFSdZofaCNFtT2coRovSIYf2hoKkPL hX/Q== X-Received: by 10.229.191.7 with SMTP id dk7mr24823088qcb.4.1381432649560; Thu, 10 Oct 2013 12:17:29 -0700 (PDT) MIME-Version: 1.0 Received: by 10.224.139.20 with HTTP; Thu, 10 Oct 2013 12:17:09 -0700 (PDT) From: Yotam Barnoy Date: Thu, 10 Oct 2013 15:17:09 -0400 Message-ID: To: Ocaml Mailing List Content-Type: multipart/alternative; boundary=001a11344d425bb54904e867da36 Subject: [Caml-list] Pattern matching on refs --001a11344d425bb54904e867da36 Content-Type: text/plain; charset=ISO-8859-1 I recently found out how ugly it is to pattern-match on a ref, using {contents=...}. This should be extremely easy to fix in the parser. Can it please be put into the next version of ocaml? ie. match x with | ref y -> ... -Yotam --001a11344d425bb54904e867da36 Content-Type: text/html; charset=ISO-8859-1
I recently found out how ugly it is to pattern-match on a ref, using {contents=...}. This should be extremely easy to fix in the parser. Can it please be put into the next version of ocaml?
ie.

match x with
| ref y -> ...

-Yotam
--001a11344d425bb54904e867da36--