From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <leo@lpw25.net>
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 B026B7EF10
	for <caml-list@sympa.inria.fr>; Mon,  9 Mar 2015 15:27:46 +0100 (CET)
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  leo@lpw25.net) identity=pra; client-ip=66.111.4.224;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="leo@lpw25.net"; x-sender="leo@lpw25.net";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  leo@lpw25.net) identity=mailfrom; client-ip=66.111.4.224;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="leo@lpw25.net"; x-sender="leo@lpw25.net";
  x-conformance=sidf_compatible
Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender
  authenticity information available from domain of
  postmaster@new2-smtp.messagingengine.com) identity=helo;
  client-ip=66.111.4.224;
  receiver=mail3-smtp-sop.national.inria.fr;
  envelope-from="leo@lpw25.net";
  x-sender="postmaster@new2-smtp.messagingengine.com";
  x-conformance=sidf_compatible
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0B+AAClrP1UnOAEb0JahDLIWwKBI00BAQEBAQEQAQEBAQEGDQkJFC6EEAEEAUA6BAsLRiwriEAIp1aFWJY3AQEBBwEBAQEBFwaLF4R1FoMBgRaKbqJthDEeMYJDAQEB
X-IPAS-Result: A0B+AAClrP1UnOAEb0JahDLIWwKBI00BAQEBAQEQAQEBAQEGDQkJFC6EEAEEAUA6BAsLRiwriEAIp1aFWJY3AQEBBwEBAQEBFwaLF4R1FoMBgRaKbqJthDEeMYJDAQEB
X-IronPort-AV: E=Sophos;i="5.11,368,1422918000"; 
   d="scan'208";a="102625418"
Received: from new2-smtp.messagingengine.com ([66.111.4.224])
  by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Mar 2015 15:27:45 +0100
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
	by mailnew.nyi.internal (Postfix) with ESMTP id 9BF28FF3
	for <caml-list@inria.fr>; Mon,  9 Mar 2015 10:27:41 -0400 (EDT)
Received: from web3 ([10.202.2.213])
  by compute1.internal (MEProxy); Mon, 09 Mar 2015 10:27:43 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=lpw25.net; h=
	message-id:x-sasl-enc:from:to:mime-version
	:content-transfer-encoding:content-type:in-reply-to:references
	:subject:date; s=mesmtp; bh=148kg5B5EVQE9MmQb7ZW8MPenVk=; b=Apa3
	wrxkMyVT4doOpAlKRrswgDKab2CH2cvfPRl9hBYcAekuLNMXXdyQvtNI4sCdIOSv
	Tw3XFUi0Hj1KzKoEsduIN/43T3vl7D0PB6b2n8icJyjN2q6HRndUj5bbqrq868OD
	5CtDFPc8AmSHsddnmOE0thbaDro4ZX3HzmQWyng=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
	messagingengine.com; h=message-id:x-sasl-enc:from:to
	:mime-version:content-transfer-encoding:content-type:in-reply-to
	:references:subject:date; s=smtpout; bh=148kg5B5EVQE9MmQb7ZW8MPe
	nVk=; b=lElI8UNer73e+x3lh6Jjtt2uoVwRVvynfH0BSvS/AkXYxqBOFSIHARBy
	pjQR20cMZUwz6dEmNEVoKLs4SsJCfYu3NYlg1ewedfQZ3vS1Yv65W3YV6P261ReP
	q/tdOcFMgYu/oGU9X1eAqx4I5UswIcwgOzGUt6B9OYwioFAVVQE=
Received: by web3.nyi.internal (Postfix, from userid 99)
	id D25321189A7; Mon,  9 Mar 2015 10:27:42 -0400 (EDT)
Message-Id: <1425911262.3240439.237866973.3128F81E@webmail.messagingengine.com>
X-Sasl-Enc: 8dJBYxT1AyTQThX0Qr7+0qipZaEnF633TnsOC0spjTkU 1425911262
From: Leo White <leo@lpw25.net>
To: caml-list@inria.fr
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain
X-Mailer: MessagingEngine.com Webmail Interface - ajax-07699171
In-Reply-To: <20150309145729.6e5d0cf0@alcazar2>
References: <54FD8397.2060002@lexifi.com> <20150309141625.0da29f2b@alcazar2>
 <54FDA20D.1000503@lexifi.com> <20150309145729.6e5d0cf0@alcazar2>
Date: Mon, 09 Mar 2015 07:27:42 -0700
Subject: Re: [Caml-list] Changing precedence and placement of attributes

> If I understand, you mean that
>   type t = int * int [@foo] * int
> would be rejected and we use instead:
>   type t = int * (int [@foo]) * int
>
> Again, it's really not natural to me.

I haven't looked at the patch closely, but it seems roughly consistent
with how "as 'a" is handled. This makes sense to me, since in both
cases you are attaching additional information to the type.

Regards,

Leo