Matthew Podwysocki

@dacz I agree it would be nice, will investigate for an FP variant

@dacz @graingert is the `pipe` mechanism we have good enough or do we need more?

@graingert that's already supported since `source` would be the first applied argument as described in the [proposal](https://github.com/tc39/proposal-pipeline-operator) ```js import { AsyncIterableX as AsyncIterable } from 'ix'; import { map, filter...

@graingert that's why we have an [`index.ts`](https://github.com/ReactiveX/IxJS/blob/master/src/iterable/index.ts) in each area root for just that purpose, as well as the [piped](https://github.com/ReactiveX/IxJS/blob/master/src/iterable/pipe/index.ts).

@patsissons but an `Array` is an `Iterable`, unless you're thinking it must be an `IterableX` type.

@jbnicolai thanks, this should be pretty easy. @azproduction any interest in this?

@blesh since there are no blocking operators allowed at that point, it'd be best if it is still a wrapped value, eg Observable. Any aggregate operations should be "async" or...

One thing that we should have is composition through some sort of `flatMap` or `concatMap` feature. This would enable such scenarios as several level deep queries. For `Array` values, it...

@ericelliott should we categorize the kinds of collections we are dealing with? For example, `Set` is different from `Map` is different from `Array` and of course `Observable`. Then perhaps you...

@ericelliott my comments were inline with having things like `add` and `push` being added but for most collections, that's simply not needed. Or you have differing APIs based upon whether...