Displaying 3 results from an estimated 3 matches for "jchoe001".
2024 Apr 05
1
Bug in out-of-bounds assignment of list object to expression() vector
On Fri, 5 Apr 2024 08:15:20 -0400
June Choe <jchoe001 at gmail.com> wrote:
> When assigning a list to an out of bounds index (ex: the next, n+1
> index), it errors the same but now changes the values of the vector
> to NULL:
>
> ```
> x <- expression(a,b,c)
> x[[4]] <- list() # Error
> x
> #> expression(NULL, N...
2024 Apr 05
1
[External] Re: Bug in out-of-bounds assignment of list object to expression() vector
On Fri, 5 Apr 2024, Ivan Krylov via R-devel wrote:
> On Fri, 5 Apr 2024 08:15:20 -0400
> June Choe <jchoe001 at gmail.com> wrote:
>
>> When assigning a list to an out of bounds index (ex: the next, n+1
>> index), it errors the same but now changes the values of the vector
>> to NULL:
>>
>> ```
>> x <- expression(a,b,c)
>> x[[4]] <- list() # Error
>&...
2024 Apr 05
3
Bug in out-of-bounds assignment of list object to expression() vector
There seems to be a bug in out-of-bounds assignment of list objects to an
expression() vector. Tested on release and devel. (Many thanks to folks
over at Mastodon for the help narrowing down this bug)
When assigning a list into an existing index, it correctly errors on
incompatible type, and the expression vector is unchanged:
```
x <- expression(a,b,c)
x[[3]] <- list() # Error
x
#>