Displaying 3 results from an estimated 3 matches for "r_expand_binding_value".
2024 Jan 18
1
Choices to remove `srcref` (and its buddies) when serializing objects
...se and because I was missing multiple private
definitions (e.g. the MAYBEJIT flag) to handle them properly.
Then there's also the problem of immediate bindings [**]: I've seen bits
of vctrs, rstudio, rlang blow up when calling CAR() on SEXP objects that
are not safe to handle this way, but R_expand_binding_value() (used by
serialize()) is again a private function that is not accessible from
packages. identical() won't help here, because it compares reference
objects (which may or may not contain such immediate bindings) by their
pointer values instead of digging down into them.
Dropping the (already v...
2024 Jan 18
1
[External] Re: Choices to remove `srcref` (and its buddies) when serializing objects
...sing multiple private
> definitions (e.g. the MAYBEJIT flag) to handle them properly.
>
> Then there's also the problem of immediate bindings [**]: I've seen bits
> of vctrs, rstudio, rlang blow up when calling CAR() on SEXP objects that
> are not safe to handle this way, but R_expand_binding_value() (used by
> serialize()) is again a private function that is not accessible from
> packages. identical() won't help here, because it compares reference
> objects (which may or may not contain such immediate bindings) by their
> pointer values instead of digging down into them.
Wha...
2024 Jan 16
2
Choices to remove `srcref` (and its buddies) when serializing objects
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 most people would think of `digest` but that package uses `serialize` (see discussion