search for: dipterix

...I think most people would think of `digest` but that package uses `serialize` (see discussion https://github.com/eddelbuettel/digest/issues/200#issuecomment-1894289875) > On Jan 12, 2024, at 11:33?AM, Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > > On 1/12/24 06:11, Dipterix Wang wrote: >> Dear R devs, >> >> I was digging into a package issue today when I realized R serialize function not always generate the same results on equivalent objects when users choose to run differently. For example, the following code >> >> serialize(with(new.e...

On 1/16/24 20:16, Dipterix Wang wrote: > Could you recommend any packages/functions that compute hash such that > the source references and sexpinfo_struct are ignored? Basically a > version of `serialize` that convert R objects to raw without storing > the ancillary source reference and sexpinfo. > I think...

...g analyses, or having to buy servers. All of these require `serialize` to produce the same results regardless of how users choose to run the code. It would be great if this feature could be in the future R. Other pipeline packages such as `targets` and `drake` can also benefit from it. Thanks, - Dipterix [[alternative HTML version deleted]]

? Tue, 16 Jan 2024 14:16:19 -0500 Dipterix Wang <dipterix.wang at gmail.com> ?????: > Could you recommend any packages/functions that compute hash such > that the source references and sexpinfo_struct are ignored? Basically > a version of `serialize` that convert R objects to raw without > storing the ancillary source ref...

...(1:2) #> [1] 70 a2 85 ef bf 3c 2c cf # vctrs semantics so dfs are vectors of rows length(vctrs:::vec_hash(mtcars)) / 4 #> [1] 32 nrow(mtcars) #> [1] 32 ``` Best, Lionel On Wed, Jan 17, 2024 at 10:32?AM Tomas Kalibera <tomas.kalibera at gmail.com> wrote: > > On 1/16/24 20:16, Dipterix Wang wrote: > > Could you recommend any packages/functions that compute hash such that > > the source references and sexpinfo_struct are ignored? Basically a > > version of `serialize` that convert R objects to raw without storing > > the ancillary source reference and sexpi...

> ------------------------------ > > Date: Wed, 17 Jan 2024 11:35:02 -0500 > > From: Dipterix Wang <dipterix.wang at gmail.com> > > To: Lionel Henry <lionel at posit.co>, Tomas Kalibera > > <tomas.kalibera at gmail.com> > > Cc: r-devel at r-project.org > > Subject: Re: [Rd] Choices to remove `srcref` (and its buddies) when > > serializi...

I also have this questions for this. I wonder if R initiates a system environment or options to instruct the packages on the number of cores to use? It doesn't have to be mandatory for now, but at least package maintainers can have shared consensus and start to adopt this humble settings rather than abusing parallel::detectCores() to max out the number of threads by default. > On Aug 7,

On Thu, 18 Jan 2024, Ivan Krylov via R-devel wrote: > ? Tue, 16 Jan 2024 14:16:19 -0500 > Dipterix Wang <dipterix.wang at gmail.com> ?????: > >> Could you recommend any packages/functions that compute hash such >> that the source references and sexpinfo_struct are ignored? Basically >> a version of `serialize` that convert R objects to raw without >> storing the...

Dear R Core devs, I wonder if it makes sense to make function file.rename return invisible? This is not a big issue, but when running in RMarkdown or knitr, this function will print results. I have to manually call invisible to hide the output from showing in the final document: ```r invisible(file.rename(...)) ``` Otherwise knitr will print: ``` file.rename(...) #> TRUE ``` If this

Dear R devs, I installed the recent devel R to test a package error when I intercept this warning when loading packages: ``` Warning in .make_numeric_version(x, strict, .standard_regexps()$valid_numeric_version) : invalid non-character version specification 'x' (type: double) ``` After a long debugging, I realize that `numeric_version` in base does not support numerical input x by