Always treat ranges as exclusive in `Range.contains?/2` #2541

Annotations

21 warnings

The following actions uses Node.js version which is deprecated and will be forced to run on node20: actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/

min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it

1..-2 has a default step of -1, please write 1..-2//-1 instead

min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it

_.._ inside match is deprecated, you must always match on the step: _.._//var or _.._//_ if you want to ignore it

min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it

min..min inside match is deprecated, you must always match on the step: min..min//var or min..min//_ if you want to ignore it

min..max inside match is deprecated, you must always match on the step: min..max//var or min..max//_ if you want to ignore it

negative steps are not supported in String.slice/2, pass 1..-2//1 instead