Hello,
Could save.image() be redesigned so that it promptly responds to Ctrl+C? It
prevents the command line from being used for a number of hours if the contents
of the workspace are large.
--
Dario Strbenac
University of Sydney
Camperdown NSW 2050
Australia
A more concrete example in order to correct my vague messages below.
Writing an R package that uses `@` and `@<-` as S3 generics. Line from manual
pages in .Rd files:
\method{@}{newclass}(object, name) <- value
Throws this error during R CMD check —as-cran
Bad \usage lines found in doc
Thank you for such a quick reply, Gabriel,
I am not too familiar with the package tools, so cannot speak too confidently,
but below is how I see the issue currently.
The issue is not for external packages to rely on unexported functions from
tools::, rather the issue is that 'R CMD check —as-cr
Karolis,
It seems likely, without having looked myself, that you could be correct
about the issue, but it does seem worth noting that both of the functions
you have mentioned are not exported, and thus not part of the API that
extension packages are allowed to use and rely on.
If retrieving the l
This issue might go deeper - I was not successful in passing R CMD checks for
the usage files. R CMD check kept showing errors for `@` declarations, even
thou they were identical to `$` declarations (which passed fine).
Seems like the usage check functions are not prepared for `@` - also in
too
I was building a package that uses the new generic @ and kept having errors
with “roxygen2” documentation. “roxygen2” generated NAMESPACE added
`@.newclass` as a newly exported function, not as a S3method.
At first I thought this must be a bug in roxygen2 and they lag behind the new
development
A tiny nit-pick nit-pick: I'd take NA to mean the finish date is missing
and you know neither whether the event has finished or if it has
finished at all :-)
Either way the proposed method seems sensible.
Tim
On 28/04/2023 16:29, Paul McQuesten wrote:
A tiny nit-pick: Seems to me that end da
A tiny nit-pick: Seems to me that end date = NA would mean the event has
not yet ended, whilst Inf would mean that the event is known to never
terminate, ie: an eternal fact, or physical law.
On Fri, Apr 28, 2023 at 10:12 AM Davis Vaughan via R-devel <
r-devel@r-project.org> wrote:
> Hi all,
>
>
Hi all,
I noticed that `range.default()` has a nice `finite = TRUE` argument,
but it doesn't actually apply to Date or POSIXct due to how
`is.numeric()` works.
```
x <- .Date(c(0, Inf, 1, 2, Inf))
x
#> [1] "1970-01-01" "Inf""1970-01-02" "1970-01-03" "Inf"
# Darn!
range(x, finite = TRUE)
