Re: [Rd] [External] undefined symbol errors when compiling package using ALTREP API

2019-06-05 Thread Mark Klik
t; The variable R_compact_intseq_class should currently be visible to > packages on all platforms, though that may change if we eventually > provide a string-based lookup mechanism, e.g. somehting like > > R_find_altrep_class("compact_intseq", "base") > > Best, > &g

Re: [Rd] [External] undefined symbol errors when compiling package using ALTREP API

2019-06-04 Thread Mark Klik
e* with the requested values > for both standard and ALTREP REALSXPs), etc. > > Does the above make sense? > > If you feel a universal API point is missing, you can raise that here, > though I can't promise that will ultimately result in the method being > added. > >

Re: [Rd] [External] undefined symbol errors when compiling package using ALTREP API

2019-06-04 Thread Mark Klik
hanks for your time & best, Mark On Tue, Jun 4, 2019 at 6:52 PM Tierney, Luke wrote: > On Tue, 4 Jun 2019, Mark Klik wrote: > > > Hello, > > > > I'm developing a package (lazyvec) that makes full use of the ALTREP > > framework (R >= 3.6.0). > >

[Rd] undefined symbol errors when compiling package using ALTREP API

2019-06-04 Thread Mark Klik
Hello, I'm developing a package (lazyvec) that makes full use of the ALTREP framework (R >= 3.6.0). One application of the package is to wrap existing ALTREP vectors in a new ALTREP vector and pass all calls from R to the contained object. The purpose of this is to provide a diagnostic framework f