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.

Sign up for GitHub

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

Jump to bottom

Update S3220: "Method calls should not resolve ambiguously" should be code smell #440

Closed
valhristov opened this issue Jun 14, 2017 · 0 comments
Closed

Update S3220: "Method calls should not resolve ambiguously" should be code smell #440

valhristov opened this issue Jun 14, 2017 · 0 comments
Labels
Type: Improvement Making existing code better.
Milestone
6.0

Comments

@valhristov
Copy link
Contributor

RSPEC-3220

The rules for method resolution are complex and perhaps not properly understood by all coders. The params keyword can make method declarations overlap in non-obvious ways, so that slight changes in the argument types of an invocation can resolve to different methods.
@valhristov valhristov added this to the 6.0 milestone Jun 14, 2017
@valhristov valhristov added Area: Rules Type: Improvement Making existing code better. labels Jun 14, 2017
@valhristov valhristov changed the title Update S3220: Method calls should not resolve ambiguously to overloads with "params" Update S3220: "Method calls should not resolve ambiguously" should be code smell Jun 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Improvement Making existing code better.
Projects
None yet
Milestone
6.0
Development

No branches or pull requests
1 participant
@valhristov