Thomas Nield
Thomas Nield
Noted, okay.
Hi @geniejhang, sorry for slow response. I've been busy with other endeavors this year. This library needs to finish migration to RxJava 3 as well as OpenJFX so I'm glad...
Thank you, I'm glad you like it. There should never be a good reason to use `subscribeOn()` against any JavaFX sources. You'll always want to use `observeOn()` to switch elements...
:thinking: Thanks for putting this reasoning together. I do agree that JavaFX ObservableCollection should be agnostic to which thread it modifies/fires on. However, I don't know if this is kosher...
Can you put in a PR, thanks!
@Wasabi375 Well by that standard, `ClosedRange` should not be inclusive then either, and it is already an incumbent range type in Kotlin. I personally think my proposed names are fine...
@Wasabi375 Or `StartExclusiveRange` and `EndExclusiveRange` :thinking:, I guess I'm not opposed to calling my proposed need `EndExclusiveRange`. **But if we are going to go that route, there's a larger issue...
With your pricing model example, you mean exclusive start ranges right? Also, I posted this on MathExchange. https://math.stackexchange.com/questions/2851657/what-are-real-world-use-cases-for-start-exclusive-ranges-intervals
I'll update the proposal and present all the approaches we discussed. I think we need to support start exclusivity after your input. Good talk.
Proposal has been updated. The new types I documented are: * `Range` * `OpenRange` * `OpenStartRange` * `OpenEndRange` @Wasabi375 I added you as a contributor, thanks for your helpful considerations...