all.equal could be improved

Open
#7,434 0 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
Needs clarification
Activity status
Stale
Tech stack
r
Domain
data

Research direction

Start with the all.equal comparison paths described in the issue, including all.equal.numeric and the ignore.row.order handling that uses setNumericRounding(). The supplied example is not reproducible and leaves the expected comparison behavior unspecified, so first establish a minimal example for d and b and define how numeric tolerance should work in both modes.

Written by the indexing model from the issue text.

Description

Not a reproducible example but clearly shows there is something to improve. When ignore.row.order=F then column by column comparison goes using all.equal.numeric method (that has tolerance), when ignore.row.order=T, then AFAIR we roll join on all fields which relies on setNumericRounding() for numeric columns.

sc = \(x) setkey(copy(x))
all.equal(d, b, ignore.row.order = TRUE)
#[1] "Dataset 'current' has rows not present in 'target'"
all.equal(sc(d), sc(b))
#[1] TRUE

1.16.2

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.