Hi
I have added a warning (r-devel r72811).
I did this rather than allow vectors for length/angle/code because ...
- consistency with (implicit) description of arguments in help page
- backward compatibility (or at least no risk of not-backwards-incompatible)
- it was easier
Note that it is onl
I was teaching new R users to make some fun graphs. I had some arrows examples
worked up we came across a problem. The arrows function ignores 2nd
and following elements of vectors given as code an angle.
Would you please consider 1) allowing vectors for code and angle, or
2) returning an error o
Greetings.
I see a warning message while compiling OpenMPI and would appreciate
it if you tell me what it means.
This warning happens with any OpenMPI > 1.6.5. Even before starting a
cluster, just "sessionInfo" triggers this warning.
I'm pasting in the message from R-3.3.2 (this is MRO).
Do th
Hello,
I have found that I cannot use sealClass() without specifying the 'where'
argument.
I have found this issue in R 3.2.3 and R 3.4.0.
For example:
> setClass("foo", slots=c(name="character", age="integer"))
> isSealedClass("foo")
[1] FALSE
> sealClass("foo")
Error in list2env(list(), NULL, )
I write to clarify the status of \U and \L when used in the replacement
argument to gsub in R 3.5.0. The behaviour of gsub appears to have changed
from R 3.4.0, but the documentation for the replacement argument has not.
## Reprex (A call to readLines is essential. A url is provided for
convenien
