From jte||er|@@rproject @end|ng |rom gm@||@com  Wed May 29 21:47:50 2019
From: jte||er|@@rproject @end|ng |rom gm@||@com (Juan Telleria Ruiz de Aguirre)
Date: Wed, 29 May 2019 21:47:50 +0200
Subject: [Rd] Converting non-32-bit integers from python to R to use bit64:
 reticulate
Message-ID: <CAJXDcw3jQd2B+hvfXuUUeczx=mmtw0MA_Udaesd-UgM+spyGJw@mail.gmail.com>

Dear R Developers,

There is an interesting issue related to "reticulate" R package which
discusses how to convert Python's non-32 bit integers to R, which has had
quite an exhaustive discussion:

https://github.com/rstudio/reticulate/issues/323

Python seems to handle integers differently from R, and is dependant on the
system arquitecture: On 32 bit systems uses 32-bit integers, and on 64-bit
systems uses 64-bit integers.

So my question is:

As regards R's C Interface, how costly would it be to convert INTSXP from
32 bits to 64 bits using C, on 64 bits Systems? Do the benefits surpass the
costs? And should such development be handled from within R Core / Ordinary
Members , or it shall be left to package maintainers?

Thank you! :)

	[[alternative HTML version deleted]]



[Rd] Converting non-32-bit integers from python to R to use bit64: reticulate
Juan Telleria Ruiz de Aguirre