Does xstream have a similar concept to rx's pipeable operators?

https://github.com/ReactiveX/rxjs/blob/master/doc/pipeable-operators.md

I’m a huge fan of FP with pipe and compose (ramda, lodash/fp), so I like that rx has a pipe fn. I also like xstream’s simplicity. Curious if xstream enables piping of some sort, sans the dot. Fns like .map and .filter make me a bit apprehensive. Patching prototypes for custom fns can get tricky, especially if the chaining hides internal mutation.

Compose seems like it might be similar to source$.pipe(fns...) in the rx link. Is it? And, if so, how easy would it be to reverse it for pipe’s redability? e.g., const pipe = (...fns)=>compose(...fns.reverse());.

Related: This mention of pipe-style api seems like it might reference the same concept, but is the only issue with the word “pipe” in it.

Thanks!

[anilanar]

I did it here: https://github.com/anilanar/xstream-pipe

[Widdershin]

Does that make sense? To summarize, more complex operators can be implemented as one-liners by applying regular pipe/compose functions to the existing set of operators (each written as fn=>stream=>stream.foo(fn)). No need to patch the prototype, or manually create producer+listener objects, unless doing something that isn’t composable from existing operators or for performance. If that’s correct, cool!

That is indeed correct 😃