-
Notifications
You must be signed in to change notification settings - Fork 63
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
Fix invalid-range-index
bug
#969
Fix invalid-range-index
bug
#969
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ch-iv thanks for making this pull request! I left a few quick comments inline.
In addition to those:
- Please update this branch from
master
; you'll find when merging that I've added a "Bug Fixes" subsection underneath "Unreleased", and you can add your CHANGELOG entry underneath that. - If you'd like to be recognized for your work, please add your name to the list of contributors in the README file :)
# Conflicts: # CHANGELOG.md
@david-yz-liu Thanks for the feedback. I just pushed all the suggested fixes to the branch. |
Pull Request Test Coverage Report for Build 6451309517
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ch-iv great work, thank you!
This PR fixes a bug where
InvalidRangeIndexChecker
would incorrectly identify invalid range calls. This PR also implements tests to test the fix. Fixes #967Motivation and Context
It solves an issue some students in CSC110 were having with range calls.
The range produces more than 1 value, however it is flagged as invalid regardless.
Your Changes
Implement a correct way of checking range calls.
Description:
Type of change (select all that apply):
Testing
Tested with hypothesis for correctness. Also unit tests provided.
Checklist