From jte||er|@@rproject @end|ng |rom gm@||@com  Mon Jun  3 06:50:17 2019
From: jte||er|@@rproject @end|ng |rom gm@||@com (Juan Telleria Ruiz de Aguirre)
Date: Mon, 3 Jun 2019 06:50:17 +0200
Subject: [Rd] 
 Converting non-32-bit integers from python to R to use bit64:
 reticulate
In-Reply-To: <23794.42957.74307.509821@stat.math.ethz.ch>
References: <CAJXDcw3jQd2B+hvfXuUUeczx=mmtw0MA_Udaesd-UgM+spyGJw@mail.gmail.com>
 <CAD4oTHH_ixXYEk1OEuFq_yJf83sDYmShbZ1nPGFovRvy-XZPnw@mail.gmail.com>
 <CAJXDcw1V=2Z0BM31Ovc5SfiUEotuHoQRqWWi5z-8UfRg2qkM5w@mail.gmail.com>
 <23794.42957.74307.509821@stat.math.ethz.ch>
Message-ID: <CAJXDcw1oP51CdTqRLvOCNGPze2mS3Y+df3SUfO=bwsHRb3nzfg@mail.gmail.com>

Thank you Martin for giving to know and developing 'Rmpfr' library for
unlimited size integers (GNU C GMP) and arbitrary precision floats (GNU C
MPFR):

https://cran.r-project.org/package=Rmpfr

My question is: In the long term (For R3.7.0 or R3.8.0):

Does it have sense that CMP substitutes INTSXP, and MPFR substitutes
REALSXP code? With this we would achieve that an integer is always an
integer, and a numeric double precision float always a numeric double
precision float, without sometimes casting underneath.

And would the R Community / R Ordinary Members would be willing to help R
Core on such implementation (If has sense, and wants to be adopted)?

Thank you all! :)


>
> If you are interested in using unlimited size integers, you
> could use the CRAN R package 'gmp' which builds on the GMP = GNU
> MP = GNU Multi Precision C library.
>
>    https://cran.r-project.org/package=gmp
>
> (and for arbitrary precision "floats", see CRAN pkg 'Rmpfr'
>  built on package gmp, and both the GNU C libraries  GMP and
>  MPFR:
>            https://cran.r-project.org/package=Rmpfr
> )
>
>

	[[alternative HTML version deleted]]



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