Thanks for the comments, feedback, and improvements.
I still argue that the current behavior cause more harm than it helps.
First of all, it increases the risk for code that does not work on all
platforms, which I'd say is one of the strengths and design goals of
R. To write cross-platform code,
Dear R-devels,
timedatectl binary used by Sys.timezone does not always work reliably.
If it doesn't the warning is raised, unnecessarily because later on
Sys.timezone gets timezone successfully from /etc/timezone. This
obviously might not be true for different linux OSes, but it solves
the issue f
Does anyone notice r-devel thread "stopifnot() does not stop at first non-TRUE
argument" starting with
https://stat.ethz.ch/pipermail/r-devel/2017-May/074179.html ?
I have mentioned
(function(...)nargs())(...)
in https://stat.ethz.ch/pipermail/r-devel/2017-May/074294.html .
Something like ..elt
