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

Closes #2475 -- setnames on a table with NA names works as expected #2477

Merged
merged 3 commits into from
Nov 13, 2017

Conversation

MichaelChirico
Copy link
Member

Other option would be something like which(!vapply(seq_along(old), function(ii) nx[ii] == old[ii], logical(1L))). Looks ugly and efficiency gain (if any) probably trivial

@codecov-io
Copy link

codecov-io commented Nov 13, 2017

Codecov Report

Merging #2477 into master will increase coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #2477      +/-   ##
==========================================
+ Coverage   91.57%   91.58%   +<.01%     
==========================================
  Files          63       63              
  Lines       12037    12044       +7     
==========================================
+ Hits        11023    11030       +7     
  Misses       1014     1014
Impacted Files Coverage Δ
R/data.table.R 97.17% <100%> (ø) ⬆️
src/fwrite.c 91.22% <0%> (+0.03%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e334ed1...7a0eb20. Read the comment docs.

@mattdowle mattdowle added this to the v1.10.6 milestone Nov 13, 2017
@mattdowle mattdowle merged commit a90d17e into master Nov 13, 2017
@mattdowle mattdowle deleted the setnames_na branch November 13, 2017 22:16
@jangorecki
Copy link
Member

jangorecki commented Nov 14, 2017

This PR broke R 3.0.0 compatibility (which is currently broken by another commit but it is irrelevant here) because there is no anyNA function in R 3.0.0. @MichaelChirico

@MichaelChirico
Copy link
Member Author

MichaelChirico commented Nov 14, 2017 via email

@jangorecki
Copy link
Member

Testing R version... makes sense for very wide tables, million of columns, which is not very common scenario but it is probably worth extra if in the code. There might be a C function in data.table code for anyNA, not sure, this would be the best to use.

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.

4 participants