Skip to content
This repository has been archived by the owner on Sep 9, 2019. It is now read-only.

Rule S3981: Collection sizes and array length comparisons should make sense #75

Closed
agigleux opened this issue Mar 9, 2018 · 1 comment · Fixed by #290
Closed

Rule S3981: Collection sizes and array length comparisons should make sense #75

agigleux opened this issue Mar 9, 2018 · 1 comment · Fixed by #290
Assignees
Labels
Milestone

Comments

@agigleux
Copy link
Member

agigleux commented Mar 9, 2018

Implements RSPEC-3981

@agigleux agigleux added this to the 1.0 milestone Mar 9, 2018
@agigleux agigleux changed the title Rule 3981: Collection sizes and array length comparisons should make sense Rule S3981: Collection sizes and array length comparisons should make sense Mar 9, 2018
@agigleux agigleux added new-rule and removed new-rule labels Mar 9, 2018
@agigleux agigleux added the to do label Mar 26, 2018
@agigleux agigleux modified the milestones: 1.0, 1.1 Mar 28, 2018
@agigleux agigleux removed the to do label Mar 28, 2018
@agigleux agigleux modified the milestones: 1.1, 1.0 Mar 29, 2018
@saberduck
Copy link
Contributor

in Go length of array or map is obtained with expression len(arr) , while in Java this is done by accessing property arr.length or calling .size() method. We can imagine tagging such expression by some SIZE kind, but this is out of scope now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants