Thanks for the report. Fixed in R-devel and R-patched (both
R-4-4-branch and R-4-3-branch).
On Fri, 5 Apr 2024, June Choe wrote:
[You don't often get email from jchoe...@gmail.com. Learn why this is important
at https://aka.ms/LearnAboutSenderIdentification ]
There seems to be a bug in out-of
Thanks all for looking into this.
Unfortunately I don't know my way around Bugzilla and I'm a bit occupied
for the next few days - it would be great if a bug report could be opened
on my behalf.
Best,
June
On Fri, Apr 5, 2024 at 10:12 AM wrote:
> On Fri, 5 Apr 2024, Ivan Krylov via R-devel wro
On Fri, 5 Apr 2024, Ivan Krylov via R-devel wrote:
On Fri, 5 Apr 2024 08:15:20 -0400
June Choe 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() #
Yes, definitely looks like a bug.
Are you able to submit it to bugs.r-project.org?
Duncan Murdoch
On 05/04/2024 8:15 a.m., June Choe wrote:
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
On Fri, 5 Apr 2024 08:15:20 -0400
June Choe 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, NULL, NUL
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 e
