Reactive: Determine future of Observable.Aliases

[clairernovotny]

How widely is System.Reactive.Observable.Aliases used? Should it remain? It cannot be merged into the single assembly as-is because of type/namespace conflicts when it's in the same assembly as the rest, so it must remain a separate assembly.

[mattpodwysocki]

@onovotny I vote to deprecate as LINQ names is the standard for .NET, not the traditional names such as flatMap, map, filter etc.

[bartdesmet]

This can be removed in any future major Rx release. The introduction of this assembly was a bad idea right from the start, but someone wanted something on their hands :-). Issues are:

• Inconsistency with the rest of .NET.
• No query provider support.
• Not aligned with standard functional variants in terms of parameter order.

[akarnokd]

Is this still relevant?

[quinmars]

The nuget package System.Reactive.Observable.Aliases is used by three github projects. Actually one of them is dotnet/reactive itself and on of them is archived, remaining steeltoe, which has 138 stars and 36 contributors after all.

[bartdesmet]

We shouldn't just take this away without first going through a phase of marking these as obsolete with an actionable item for users to move to the standard operators. I'm happy to take that route and enable us to take these out in a subsequent release. Tentatively moving to the upcoming release milestone.