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.

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

correctness::sub_range_types::sub_range_chooses_right_implementation #625

Closed
Tracked by #529
99NIMI opened this issue Nov 3, 2022 · 0 comments · Fixed by #626
Closed
Tracked by #529

correctness::sub_range_types::sub_range_chooses_right_implementation #625

99NIMI opened this issue Nov 3, 2022 · 0 comments · Fixed by #626
Assignees

Comments

@99NIMI
Copy link
Member

99NIMI commented Nov 3, 2022

issue: parameters and return type of SubRange check functions not casted to correct type

@99NIMI 99NIMI self-assigned this Nov 3, 2022
99NIMI added a commit to 99NIMI/rusty that referenced this issue Nov 3, 2022

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
@99NIMI 99NIMI linked a pull request Nov 3, 2022 that will close this issue
99NIMI added a commit to 99NIMI/rusty that referenced this issue Nov 3, 2022
99NIMI added a commit to 99NIMI/rusty that referenced this issue Nov 10, 2022
ghaith added a commit that referenced this issue Nov 10, 2022
* #625 sub_range check functions refactor

* #625 fix test

* #625 refactor, use id_provider, rename

Co-authored-by: Ghaith Hachem <ghaith.hachem@gmail.com>
@ghaith ghaith moved this to Done in Next Jan 9, 2023
@ghaith ghaith added this to Next Jan 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant