Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Retain with=FALSE behavior in more j=call:call cases like 1:ncol(DT) #6487

Merged
merged 5 commits into from
Sep 9, 2024

Conversation

MichaelChirico
Copy link
Member

#6486 -- not closing, I haven't verified this fixes every case. I'll wait for revdeps report to formally close.

I removed these tests DT[1L, t:max(t)] + DT[1L, min(t):t] because this change broke them, and it's not clear to me such usage is practical anyway (it only makes sense on a 1-row subset). We can revisit later IMO.

Copy link

github-actions bot commented Sep 8, 2024

Comparison Plot

Generated via commit 8cf21c7

Download link for the artifact containing the test results: ↓ atime-results.zip

Time taken to finish the standard R installation steps: 11 minutes and 57 seconds

Time taken to run atime::atime_pkg on the tests: 6 minutes and 39 seconds

Copy link
Member

@jangorecki jangorecki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this removed tests doesn't look very useful.
When moving to 2.0 we should drop a lot of support in those NSE tricks IMO. Code was already pretty complex and it only getting worse now.
But +1 for better escaping NSE with with=F

@MichaelChirico MichaelChirico merged commit 09c7518 into master Sep 9, 2024
7 of 8 checks passed
@MichaelChirico MichaelChirico deleted the col_range_with branch September 9, 2024 15:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants