Auto instrumentation of Services

[patroza]

tracing: true would wrap all service members with

Effect.withSpan(`${identifier}.${member}`)

(or the new upcoming Effect.fn)

complications:

• non effect returning functions

Can look into andThen implementation for some ideas.
Can look at only allowing the tracing: true option when shape is compatible.
Either use proxy or just a Record.map

Alternatives:

• tsc/loader plugin to wrap functions automatically with Effect.fn?

[jfet97]

Reference: Effect-TS/effect#3938

[jfet97]

Effect.fn should support normal functions too, right?

[mikearnaldi]

Effect.fn should support normal functions too, right?

Effect.fn supports generators and Effect-returning functions

[jfet97]

Effect.fn should support normal functions too, right?

Effect.fn supports generators and Effect-returning functions

I misunderstood a comment in the source code then, thanks! Even tho it could accept non Effect-returning function and wrap the result with Effect.succed/Effect.fail. I suppose.

[patroza]

Maybe best solution is that the Service constructor passes a { fn }, that you can destructure, and so you can easily return { a: fn(function*() {}) } etc?