-
Notifications
You must be signed in to change notification settings - Fork 187
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
New object_overwrite_linter #2307
Conversation
There are a couple dozen hits on {lintr}:
|
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2307 +/- ##
==========================================
- Coverage 99.40% 99.38% -0.02%
==========================================
Files 118 119 +1
Lines 5355 5392 +37
==========================================
+ Hits 5323 5359 +36
- Misses 32 33 +1 ☔ View full report in Codecov by Sentry. |
Another idea could be to have another argument like
|
That sounds like a great idea. |
done |
Metadata + vectorization tests are missing. |
Part of #884
Here's another one we didn't end up using internally, so it hasn't gotten all too much scrutiny -- it might benefit from some rethinking (e.g. is exclusion of top-level assignments and function formals really necessary? Or even worth putting behind an argument?)
Originally, we also used a fixed set of functions to check for duplicates based on the observed frequency of overwrites in our code base. Presenting that list for posterity, but I'm not sure there's a "principled" way to include it in the general package: