style(scan): updated signatures for scan and reduce

[david-driscoll]

Description:
This change makes working with scan/reduce a little easier in TypeScript based applications.

Related issue (if exists):
None that I'm aware of.

This change makes working with scan and reduce a little easier without having to cast the types.

[coveralls]

Coverage remained the same at 96.707% when pulling 6d54973 on david-driscoll:scan-signature into 1590304 on ReactiveX:master.

[paulpdaniels]

Is there any danger in combining the two signature interfaces since they are identical?

[kwonoj]

Is there any danger in combining the two signature interfaces since they are identical?

: Yes, interesting point. Signature seems could be reused, most pain point maybe having good name for common type?

[david-driscoll]

The common name I would go with is reduce, simply because they are both reduce operations. reduce just happens on complete, and scan happens on next.

[kwonoj]

for me those name looks fine.

[benlesh]

Nice work @david-driscoll

[david-driscoll]

Branch updated.

[coveralls]

Coverage remained the same at 96.722% when pulling 1bd06a6 on david-driscoll:scan-signature into e366734 on ReactiveX:master.

[kwonoj]

LGTM

[kwonoj]

@david-driscoll , would you able to check PR? it still says diverged from master, not able to merge.

[david-driscoll]

Whoops, one sec.

[david-driscoll]

Rebased.

[coveralls]

Coverage remained the same at 96.722% when pulling b447525 on david-driscoll:scan-signature into e366734 on ReactiveX:master.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.