Was just taking a deeper look at XVector and wondered whether the concept
of an XVector being a single-range view of a Shared* object (essentially an
R vector wrapped in an externalptr to avoid copying?) could be applied to
iteration, where we could slide that range to represent each partition, for
On 11/15/2013 10:22 AM, Michael Lawrence wrote:
Doesn't look like genomeIntervals has any C code (?), so a performance
comparison would be interesting. rtracklayer jumps through all sorts of
hoops to handle obscure things like URL encoding in GFF3. The code in
genomeIntervals seems more streamlin
Doesn't look like genomeIntervals has any C code (?), so a performance
comparison would be interesting. rtracklayer jumps through all sorts of
hoops to handle obscure things like URL encoding in GFF3. The code in
genomeIntervals seems more streamlined.
On Fri, Nov 15, 2013 at 10:14 AM, Nicola
Took that thread to the devel list, just feels more appropriate with regards to
the content.
I already have that on my TODO list :-). This is not up-to-date, i.e. I haven’t
done the comparison in ~2 years, but last time I did, genomeIntervals attribute
parsing was faster than rtracklayer equiva
