Clarification on `Effect.tap` Function Return Type and Potential Risks
Hi there! Quick question around the type of
Effect.tap: What's the reason behind accepting any kind of result for the function? To me, tap is used to trigger side effects so it makes sense to require an Effect to be returned by the function. With the current types, I find it "dangerous" as you can easily forget to return your effect or return something else (let's say a readerTaskEither if you are in the process of migrating from fp-ts) cc @laur__e
