search for: elt_method

...an unnecessary duplication of the data. In order to return CHARSXPs to R, It forces me to allocate CHARSXPs and copy the entire data to the R process. By contrast, for the other ALTREP types, say altreal, I can just return the pointer to R if the data is in the memory. The same problem occurs for Elt_method as well but is less serious since only one CHARSXPs is allocated. Because my package is designed for sharing a large R object. An allocation of the memory is undesired especially when the data is read-only in the code(eg. print function). I'm not sure if there are any solutions existed in the c...

...order to return >> CHARSXPs to R, It forces me to allocate CHARSXPs and copy the entire data >> to the R process. By contrast, for the other ALTREP types, say altreal, I >> can just return the pointer to R if the data is in the memory. >> >> The same problem occurs for Elt_method as well but is less serious since >> only one CHARSXPs is allocated. Because my package is designed for sharing >> a large R object. An allocation of the memory is undesired especially when >> the data is read-only in the code(eg. print function). I'm not sure if >> ther...

...ion of the data. In order to return > CHARSXPs to R, It forces me to allocate CHARSXPs and copy the entire data > to the R process. By contrast, for the other ALTREP types, say altreal, I > can just return the pointer to R if the data is in the memory. > > The same problem occurs for Elt_method as well but is less serious since > only one CHARSXPs is allocated. Because my package is designed for sharing > a large R object. An allocation of the memory is undesired especially when > the data is read-only in the code(eg. print function). I'm not sure if > there are any soluti...

...>> CHARSXPs to R, It forces me to allocate CHARSXPs and copy the entire data >>> to the R process. By contrast, for the other ALTREP types, say altreal, I >>> can just return the pointer to R if the data is in the memory. >>> >>> The same problem occurs for Elt_method as well but is less serious since >>> only one CHARSXPs is allocated. Because my package is designed for sharing >>> a large R object. An allocation of the memory is undesired especially when >>> the data is read-only in the code(eg. print function). I'm not sure if &...