Displaying 15 results from an estimated 15 matches for "class__".
2019 Nov 02
6
head.matrix can return 1000s of columns -- limit to n or add new argument?
...d classes, which I sense that we'd rather not do....
>
> and we have something like that already with is(.)
>
> Thank you for these important points raised!
>
> Note again that both "matrix" and "array" are special [see ?class] as
> being of __implicit class__ and I am considering that this
> implicit class behavior for these two should be slightly changed
> such that
>
> foo <- function(x,...) UseMethod("foo")
> foo.array <- function(x, ...)
> sprintf("array of dim. %s", paste(dim(x), collapse...
2019 Nov 10
2
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...eak -- unless we change class(x) to return the whole
>> set of inherited classes, which I sense that we'd rather not do....
>
> [................]
>
>> Note again that both "matrix" and "array" are special [see ?class] as
>> being of __implicit class__ and I am considering that this
>> implicit class behavior for these two should be slightly
>> changed ....
>>
>> And indeed I think you are right on spot and this would mean
>> that indeed the implicit class
>> "matrix" should rather become c("ma...
2019 Oct 31
2
head.matrix can return 1000s of columns -- limit to n or add new argument?
Hmm, the problem I see here is that these implied classes are all inherently one-off. We also have
> inherits(matrix(1,1,1),"numeric")
[1] FALSE
> is.numeric(matrix(1,1,1))
[1] TRUE
> inherits(1L,"numeric")
[1] FALSE
> is.numeric(1L)
[1] TRUE
and if we start fixing one, we might need to fix all.
For method dispatch, we do have inheritance, e.g.
>
2019 Nov 14
2
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...k -- unless we change class(x) to return the whole
> > set of inherited classes, which I sense that we'd rather not do....
>
> [................]
>
> > Note again that both "matrix" and "array" are special [see ?class] as
> > being of __implicit class__ and I am considering that this
> > implicit class behavior for these two should be slightly
> > changed ....
> >
> > And indeed I think you are right on spot and this would mean
> > that indeed the implicit class
> > "matrix" should rather become c(&qu...
2019 Nov 01
0
head.matrix can return 1000s of columns -- limit to n or add new argument?
...eturn the whole set of inherited classes, which I sense that we'd rather not do....
and we have something like that already with is(.)
Thank you for these important points raised!
Note again that both "matrix" and "array" are special [see ?class] as
being of __implicit class__ and I am considering that this
implicit class behavior for these two should be slightly changed
such that
foo <- function(x,...) UseMethod("foo")
foo.array <- function(x, ...)
sprintf("array of dim. %s", paste(dim(x), collapse = " x "))
should w...
2019 Nov 02
0
head.matrix can return 1000s of columns -- limit to n or add new argument?
...t we'd rather not do....
>>
>> and we have something like that already with is(.)
>>
>> Thank you for these important points raised!
>>
>> Note again that both "matrix" and "array" are special [see ?class] as
>> being of __implicit class__ and I am considering that this
>> implicit class behavior for these two should be slightly changed
>> such that
>>
>> foo <- function(x,...) UseMethod("foo")
>> foo.array <- function(x, ...)
>> sprintf("array of dim. %s",...
2019 Nov 11
2
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...t; set of inherited classes, which I sense that we'd rather not do....
>>>
>>> [................]
>>>
>>>> Note again that both "matrix" and "array" are special [see ?class] as
>>>> being of __implicit class__ and I am considering that this
>>>> implicit class behavior for these two should be slightly
>>>> changed ....
>>>>
>>>> And indeed I think you are right on spot and this would mean
>>>> that indeed the implicit class...
2019 Nov 10
0
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...t; > which would break -- unless we change class(x) to return the whole
> set of inherited classes, which I sense that we'd rather not do....
[................]
> Note again that both "matrix" and "array" are special [see ?class] as
> being of __implicit class__ and I am considering that this
> implicit class behavior for these two should be slightly
> changed ....
>
> And indeed I think you are right on spot and this would mean
> that indeed the implicit class
> "matrix" should rather become c("matrix", "array&q...
2019 Nov 10
0
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...class(x) to return the whole
>>> set of inherited classes, which I sense that we'd rather not do....
>>
>> [................]
>>
>>> Note again that both "matrix" and "array" are special [see ?class] as
>>> being of __implicit class__ and I am considering that this
>>> implicit class behavior for these two should be slightly
>>> changed ....
>>>
>>> And indeed I think you are right on spot and this would mean
>>> that indeed the implicit class
>>> "matrix" should r...
2019 Nov 14
0
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...class(x) to return the whole
>>> set of inherited classes, which I sense that we'd rather not do....
>>
>> [................]
>>
>>> Note again that both "matrix" and "array" are special [see ?class] as
>>> being of __implicit class__ and I am considering that this
>>> implicit class behavior for these two should be slightly
>>> changed ....
>>>
>>> And indeed I think you are right on spot and this would mean
>>> that indeed the implicit class
>>> "matrix" should r...
2019 Nov 12
0
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...which I sense that we'd rather not do....
> >>>
> >>> [................]
> >>>
> >>>> Note again that both "matrix" and "array" are special [see ?class] as
> >>>> being of __implicit class__ and I am considering that this
> >>>> implicit class behavior for these two should be slightly
> >>>> changed ....
> >>>>
> >>>> And indeed I think you are right on spot and this would mean
> >>>> t...
2019 Nov 15
5
class(<matrix>) |--> c("matrix", "arrary") [was "head.matrix ..."]
...t; set of inherited classes, which I sense that we'd rather not do....
>>>
>>> [................]
>>>
>>>> Note again that both "matrix" and "array" are special [see ?class] as
>>>> being of __implicit class__ and I am considering that this
>>>> implicit class behavior for these two should be slightly
>>>> changed ....
>>>>
>>>> And indeed I think you are right on spot and this would mean
>>>> that indeed the implicit class...
2020 Jan 21
2
class(<matrix>) |--> c("matrix", "arrary") -- and S3 dispatch
...gt; >>> On Sun, Nov 10, 2019 at 2:37 AM Martin Maechler ... wrote:
>
> [................]
>
> >>>>> Note again that both "matrix" and "array" are special [see ?class] as
> >>>>> being of __implicit class__ and I am considering that this
> >>>>> implicit class behavior for these two should be slightly
> >>>>> changed ....
> >>>>>
> >>>>> And indeed I think you are right on spot and this would mean
> &g...
2019 Nov 21
0
class(<matrix>) |--> c("matrix", "arrary") -- and S3 dispatch
...4/19 05:47, Hadley Wickham wrote:
>>> On Sun, Nov 10, 2019 at 2:37 AM Martin Maechler ... wrote:
[................]
>>>>> Note again that both "matrix" and "array" are special [see ?class] as
>>>>> being of __implicit class__ and I am considering that this
>>>>> implicit class behavior for these two should be slightly
>>>>> changed ....
>>>>>
>>>>> And indeed I think you are right on spot and this would mean
>>>>> that indee...
2020 Jan 28
0
class(<matrix>) |--> c("matrix", "arrary") -- and S3 dispatch
...; On Sun, Nov 10, 2019 at 2:37 AM Martin Maechler ... wrote:
>>
>> [................]
>>
>> >>>>> Note again that both "matrix" and "array" are special [see ?class] as
>> >>>>> being of __implicit class__ and I am considering that this
>> >>>>> implicit class behavior for these two should be slightly
>> >>>>> changed ....
>> >>>>>
>> >>>>> And indeed I think you are right on spot and this would mean...