Assignment is inconsistent with list

Open
#4,569 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
data

Research direction

Start by reproducing the single-row and multi-row examples in R, then inspect the linked [ .data.table method in R/data.table.R around lines 1047-1053. Determine the intended coercion for var := .(...) versus :=(var = .(...)); done means the assignment forms behave consistently for equal and non-equal lengths.

Written by the indexing model from the issue text.

Description

consistency non-atomic column

Updating a data.table by reference provides inconsistent results for single-row data.tables:

library(data.table) ##1.12.8 - same results in master
dt = data.table(a = 3L)
dt[, b:= 3L]
dt[, b2 := .(3L)]
dt[, `:=`( b3 = 3L)]
dt[, `:=`(b4 = .(3L))]
dt
#>        a     b    b2    b3     b4
#>    <int> <int> <int> <int> <list>
#> 1:     3     3     3     3      3

Basically, the var := .(...) version seems to coerce the RHS to an atomic if ... evaluates to an atomic and is the same number of rows as the data.table. This differs from `:=`(var = .(...)) which appears to always make var a list column

dt = data.table(a = c(1L,3L))
dt[, b2 := .(c(2L, 3L))]
dt[, `:=`(b4 = .(c(2L, 3L)))]
dt

##       a    b2     b4
##   <int> <int> <list>
##1:     1     2    2,3
##2:     3     3    2,3

##non-equal lengths
dt = data.table(a = c(1L, 3L, 5))
dt[, b2 := .(c(2L, 3L))]
dt

##       a     b2
##   <num> <list>
##1:     1    2,3
##2:     3    2,3
##3:     5    2,3

I have not had a chance to dig deep, but this line from [.data.table may help explain why `:=`(var = .(...)) results in a list.

https://github.com/Rdatatable/data.table/blob/ad7b67c80a551b7a1e2ef8b73d6162ed7737c934/R/data.table.R#L1047-L1053

This was observed while investigating #4568 although I am not sure how related they are.

Dominant language
R
Stars
3.9k
Forks
1.1k
Avg merge
14h 4m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rdatatable/data.table

All issues in Rdatatable/data.table

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.