`Effect.serviceMembers` (and variants) do not recognize `Stream` returning members

Question

Opened this issue a year ago · 6 comments

interface Foo {
  foo: Stream.Stream<never,never,number>
}
const tag = Context.Tag<Foo>()
const { foo /* <- nop */ } = Effect.serviceConstants(tag)

Answer 1 · 2023-09-05T13:47:37.000Z

Answer 2 · 2023-09-06T11:06:21.000Z

Answer 3 · 2023-09-06T14:36:00.000Z

Oh indeed the focus was on Effects, may have a look later in the week

Answer 4 · 2023-09-06T15:08:00.000Z

Stream is not part of Effect/io

P.S.: This can wait for the great reunification of "everything is a Stream" (Londonian joke for @mikearnaldi)

Answer 5 · 2023-09-06T18:33:46.000Z

But it looks really lame 🥲

Answer 6 · 2023-09-08T06:44:50.000Z

@datner I agree,
I found out it can be an invaluable tool to reduce boilerplate for some particular usages.

@mikearnaldi any thinking on if we want to tackle this?

Ideas:

Implement it in effect/stream and let the user aggregate both results
Implement aggregation out of io and stream but exposed via effect (where?)