-
Notifications
You must be signed in to change notification settings - Fork 624
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
More support for ranges #3736
Comments
I think add support shouldBeIn range would be hard. But maybe creating new function can be solution. |
got it. how about this |
think we have to specify which type we should accept only range? or other list types |
if maintainer says yes maybe I can add method to support this proposal |
only ranges. It does not make sense for lists |
What about
|
let's use these function names |
Assigned to you |
I think there should be some careful approaches about ranges since it has backward range |
and think we need to add support for until |
backwards or forwards, still comprises a set of numbers, so within should be fine. |
I'd also enforce that we should try to go for an strictly correct mathematical definition. Sets theory is very well defined, ie
|
I will release 5.8.1 from what is on main in a few days, then whatever comes after will move to 5.9 which is will be kotlin 1.9+ |
implemented only intersect #3792 |
Linked: #3736 Co-authored-by: Leonardo Colman Lopes <dev@leonardo.colman.com.br>
Examples:
(0..2) shouldOverlapWith (1..3)
(2..3) shouldBeIn (1..4)
(0..1) shouldNotOverlapWith (2..3)
(4..5) shouldNotBeIn (1..3)
should support both ClosedRange and OpenEndRange.
I'd like to do it if this feature is needed.
The text was updated successfully, but these errors were encountered: