From d@n+r-deve| @end|ng |rom kort@ch@k@|o  Tue Sep  8 10:59:40 2020
From: d@n+r-deve| @end|ng |rom kort@ch@k@|o (Dan Kortschak)
Date: Tue, 08 Sep 2020 08:59:40 +0000
Subject: [Rd] some questions about R internal SEXP types
In-Reply-To: <CAOdV3zA-cFvDvyV-pvx6NDpk7EBmOXBDv_w01P6qdHnFQtqLNg@mail.gmail.com>
References: <8f4d92d753e266a0c8a303b9a354a42a071b24bf.camel@kortschak.io>
 <1ec817ab612c4cf782b15f8150364ad4ff3b306b.camel-2274@kortschak.io>
 <CAOdV3zA-cFvDvyV-pvx6NDpk7EBmOXBDv_w01P6qdHnFQtqLNg@mail.gmail.com>
Message-ID: <cd798e24c9fc3b7a8d6adc4d70a73edca6c8ee92.camel@kortschak.io>

Thanks, Alex.

That might be good enough for me for this particular concern; in the
absence of a language specification specifying my behaviour and
referring to precedent seems like a reasonable fall back.

Dan

On Tue, 2020-09-08 at 09:33 +0200, Bertram, Alexander wrote:
> Hi Dan,
> 
> For what it's worth, Renjin requires LISTSXPs to hold either a
> LISTSXP or a NULL, and this appears to be largely the case in
> practice based on running tests for thousands of packages (including
> cross compiled C code). I can only remember it being briefly an issue
> with the rlang package, but Lionel graciously changed it:
> https://github.com/r-lib/rlang/pull/579
> 
> Best,
> Alex



[Rd] some questions about R internal SEXP types
Dan Kortschak