-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Moving towards fast evaluation (unwindProtect) by default #1227
Comments
(Just curious here: should the checkmarks above not be open until the respective PRs have been merged?) Thanks for filing all those PRs. Our machine is well oiled 😀 |
In this case, I used the checkmarks to denote that I need to do something (that is, if they're not checked). When the PRs are merged, we'll see the links above change color. And when they hit CRAN, I'll add a note. |
Oh, wow, neat! I was unaware of that link trick. I did notice that GitHub started to expand them, I do notice now that they have the open pull request logo. (Still, to me the tick is for final completion. But details schmetails. You are running with this -- and thanks for that -- so your rules. |
switch to define following RcppCore/Rcpp#1227
switch to define following RcppCore/Rcpp#1227
switch to define following RcppCore/Rcpp#1227
switch to define following RcppCore/Rcpp#1227
switch to define following RcppCore/Rcpp#1227
Wanted to clarify: if I am using function |
If you are just using |
If I recall, (and sorry for the lack of context; conference brain) there was one issue with |
It was Jeroen's V8. The code path that was failing required a And packages can still call |
Okay, great. Thanks! |
Yeah, as I recall Jeroen fixed that promptly and early and it already wasn't an issue on 1.0.8. All good 😸 |
Updated versions now on CRAN for packages isotree, MatrixExtra, outliertree, readsparse, recometrics. |
Updated version now on CRAN for package FIESTAutils. |
This is now fully complete as Rcpp 1.0.10 is now on CRAN. 🎇 |
Unwind protection for fast evaluation of R code at C/C++ level was introduced in R 3.5, and it has been supported as an opt-in since Rcpp 0.12.15 via a define (
RCPP_USE_UNWIND_PROTECT
) and a plugin (unwindProtect
). Now #1225 brings this as a default for the next release:RCPP_USE_UNWIND_PROTECT
has no effect anymore.RCPP_NO_UNWIND_PROTECT
.To plan ahead for this eventual removal (and avoid warnings as much as possible meanwhile), we'll try to identify all the packages using the plugin and propose a patch to switch to using
RCPP_USE_UNWIND_PROTECT
, which is harmless when the feature is enabled by default. This issue will keep track of the process.Done
The text was updated successfully, but these errors were encountered: