Match System.Reactive namespaces #9
Labels
enhancement
New feature or request
Milestone
Comments
kzu
added a commit
that referenced
this issue
Sep 28, 2021
This makes RxFree a 100% compatible drop-in replacement if only the provided types are used in a given project. Likewise, if the need arises for feature not provided in RxFree, it's trivial to "migrate" to System.Reactive: just uninstall RxFree and install System.Reactive and start using whatever is missing from this project. Fixes #9
kzu
added a commit
that referenced
this issue
Sep 28, 2021
This makes RxFree a 100% compatible drop-in replacement if only the provided types are used in a given project. Likewise, if the need arises for feature not provided in RxFree, it's trivial to "migrate" to System.Reactive: just uninstall RxFree and install System.Reactive and start using whatever is missing from this project. Fixes #9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we provide all types in the top-level
Systemnamespace, which makes consumption straightforward but which isn't 100% compatible with System.Reactive.For example, Rx uses
System.Reactive.Linqfor theOfType/Where/Selectextension methods,System.Reactive.SubjectsandSystem.Reactive.Disposables.Even though using separate namespaces for just one or two types (in our case) would seem unnecessary, by not using the same namespaces as
System.Reactive, this package is not a simple drop-in replacement (neither can it be replaced by just switching to the full Rx package), since compilation errors will need fixing from the namespace mismatches.We should instead be 100% compatible so that switching packages is all that's needed.
The text was updated successfully, but these errors were encountered: