-
-
Notifications
You must be signed in to change notification settings - Fork 182
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
[Feature]: #963
Comments
Additional scenarios we discussed... using var subscription = changes
.Sort()
.Transform() // Does not preserve properties needed for sorting
.Bind()
.Subscribe(); var sharedChanges = changes
.Sort()
.Publish();
using var subscription1 = sharedChanges
.Bind()
.Subscribe();
using var subscription2 = sharedChanges
.Bind()
.Subscribe();
using var connection = sharedChanges
.Connect(); The second scenario is pretty compelling to me, as a potential performance improvement for not duplicating sort work. However, I also proposed in the thread that the performance of |
I think I came across another scenario where there's a use case for sorting before binding. If the output collection is a base type, but the observable stream coming in is a derived type. If there's an elegant work around I'm not seeing, please let me know :)
|
Describe the functionality desired 🐞
With the .Sort() method being depreciated there are a couple of rare cases where applying a sort immediately is desired because the properties used in the comparison do not exist downstream.
example:
Changing the call chain to use SortAndBind() is not possible in this scenario.
I had a conversation on Slack about this topic:
https://reactivex.slack.com/archives/C4LF8S19N/p1733511277945719
The steps the functionality will provide
Considerations
SortAndBind
The text was updated successfully, but these errors were encountered: