radfordneal

4 ms·

1. 1.▲
   by radfordneal 13y ago

   Sort of. That's why it shouldn't be too hard a modification to implement. For a call-by-name argument, you just have to evaluate the "promise" every time, rather than just the first time. (Assignment to a call-by-name
2. 2.▲
   by radfordneal 13y ago

   It's difficult to see how this rationale can possibly justify ignoring a 10x speed up in vector-matrix multiplies (and similar speedups for some other matrix multiplies) that can be achieved with a modification affecting a dozen or so
3. 3.▲
   by radfordneal 13y ago

   At present, pqR waits for all helper threads to be idle before doing a fork in the "parallel" package, and disables use of helper threads in the child processes (and temporarily in the parent, since it will wait for the child proc
4. 4.▲
   by radfordneal 13y ago

   Yes, it's part of the release, and is also directly linked at radfordneal.github.io/pqR
5. 5.▲
   by radfordneal 13y ago

   If you look at the "future directions" section of pqR's version of the "R Internals" manual, you'll see a brief mention of a plan to implement "call by name" parameter passing in the style of Algol 60
6. 6.▲
   by radfordneal 13y ago

   At present, pqR is compatible with Rstudio only if you configure with the --disable-helper-threads option (ie, no automatic parallelization) along with the --enable-R-shlib option that's needed for Rstudio. This is a minor glitch in h