Order of Generics on Zip Operator

[benjchristensen]

I just noticed that the zip operator has generics ordered as <R, T0, T1, T2, T3>.

This differs from Rx.Net and Func* classes which are like Func4<T1, T2, T3, T4, R>.

This would be a breaking change, but should we do it to get consistency of ordering the return type always as the last generic?

[benjchristensen]

Maybe we get 0.12.0 out the door with #331 right away so it comes along with most people picking up the breaking changes in 0.11.0 as well?

[jmhofer]

I agree, these generics should be reordered for consistency.

I'll hurry with #331 as it will get difficult to merge as soon as more changes happen. - There's probably still a lot more Observable usages that can be generalized, though...

[abersnaze]

Definitely. I was thinking that any incompatibilities rx JavaScript and
Java implementations might be a deal breaker for kotlin.

On Saturday, August 31, 2013, Joachim Hofer wrote:

I agree, these generics should be reordered for consistency.

I'll hurry with #331 #331 as it
will get difficult to merge as soon as more changes happen. - There's
probably still a lot more Observable usages that can be generalized,
though...

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/333#issuecomment-23615247
.

[benjchristensen]

I have submitted these changes to jmhofer#1 for inclusion in #331