[Rcpp-devel] [small ann] Sparse++

2016-12-30 Thread Dmitriy Selivanov
Hello mailing list. Just small announcement. I made package "sparsepp" which brings bindings to header only 'sparsepp' library - https://github.com/greg7mdp/sparsepp. It is on CRAN already. Sparse++ is improvement over google sparse hash library (see this write-up https://github.com/greg7mdp/spar

Re: [Rcpp-devel] [small ann] Sparse++

2016-12-30 Thread Dirk Eddelbuettel
On 30 December 2016 at 15:49, Dmitriy Selivanov wrote: | Hello mailing list. Just small announcement. I made package "sparsepp"  which | brings bindings to header only 'sparsepp' library  - https://github.com/ | greg7mdp/sparsepp. It is on CRAN already. Sparse++ is improvement over google | sparse

Re: [Rcpp-devel] Rcpp Timer

2016-12-30 Thread Dirk Eddelbuettel
On 29 December 2016 at 11:25, Jonathan Christensen wrote: | Hi Kaspar and Dirk, | | It is indeed cumulative. Previously (presumably when that gallery page was | written) it was not cumulative, but Romain Francois changed the behavior of the | step() function several years ago, in this commit:  h

Re: [Rcpp-devel] Rcpp Timer

2016-12-30 Thread Dirk Eddelbuettel
On 30 December 2016 at 06:37, Dirk Eddelbuettel wrote: | | On 29 December 2016 at 11:25, Jonathan Christensen wrote: | | Hi Kaspar and Dirk, | | | | It is indeed cumulative. Previously (presumably when that gallery page was | | written) it was not cumulative, but Romain Francois changed the beha

Re: [Rcpp-devel] Rcpp Timer

2016-12-30 Thread Romain Francois
It made more sense to track times since an origin, esp when you might use several timers in case you use multiple threads. > Le 30 déc. 2016 à 13:37, Dirk Eddelbuettel a écrit : > > > On 29 December 2016 at 11:25, Jonathan Christensen wrote: > | Hi Kaspar and Dirk, > | > | It is indeed cumu

Re: [Rcpp-devel] Rcpp Timer

2016-12-30 Thread Dirk Eddelbuettel
On 30 December 2016 at 20:38, Romain Francois wrote: | It made more sense to track times since an origin, esp when you might use several timers in case you use multiple threads. Using an offset to an origin (and hence differences) is also a sensible way to deal with higher resolutions. We cann