Fix how we check if a range expression covers one value. #815
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
My previous fix, #806, had the wrong logic to determine if a confirmation's expected count as-a-
RangeExpression
had exactly one value, so we were printing sub-optimal messages on test failures. Specifically, this:Would report "1...1 time(s)" instead of "1 time".
Checklist: