Simplify generated attributes code for RNGScope #248
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use RObject and it's destructor rather than SEXP protect/unprotect. The code we were generating was correct however hard to read and reason about for users not familiar with R/Rcpp internals. Previously we held the result in a raw SEXP which we unprotected after leaving a special block created for the RNGScope:
Now, we simply construct an RObject prior to the RNGScope on the stack and then return that object (this ensures that any GC triggered by PutRNGState won't collect the result SEXP before it can be returned):