Displaying 3 results from an estimated 3 matches for "r47934".
Did you mean:
147934
2020 Oct 26
0
Change to I() in R 4.1
...17794
https://bugs.r-project.org/bugzilla/show_bug.cgi?id=17794
and the direct dangerous `call<-` will be replaced happily in
I()'s definition.
*But* as Luke Tierney had remarked to R-core, direct changing of
the class of an S4 object has given the above warning for a
quite while, (svn r47934 | jmc | 2009-02-17 )
*and* it has rather been an inconsistency in R, that you could
still use "low-level" means to change the class of an S4 object
to something invalid.
I really don't think people should be allowed to use I() to
change a valid S4 object into an invalid one, but this...
2020 Oct 23
2
Change to I() in R 4.1
Hi there,
Is that change in R-devel intentional?
library(Matrix)
m <- as(matrix(c(0, 1)), "sparseMatrix")
isS4(m)
# [1] TRUE
x <- I(m)
# Warning message:
# In `class<-`(x, unique.default(c("AsIs", oldClass(x)))) :
# Setting class(x) to multiple strings ("AsIs", "dgCMatrix", ...);
result will no longer be an S4 object
2020 Oct 30
2
Change to I() in R 4.1
...hZHZYnpQxPGEZdZPgTHMkKg&e=
>
> and the direct dangerous `call<-` will be replaced happily in
> I()'s definition.
>
> *But* as Luke Tierney had remarked to R-core, direct changing of
> the class of an S4 object has given the above warning for a
> quite while, (svn r47934 | jmc | 2009-02-17 )
> *and* it has rather been an inconsistency in R, that you could
> still use "low-level" means to change the class of an S4 object
> to something invalid.
>
> I really don't think people should be allowed to use I() to
> change a valid S4 object...