What is the problem this feature would solve?
-
using Effect.fnUntraced() to define class methods (when tracing is not needed)
-
consistency with Effect.fn() API (I ran into this when I realized I didn't need Effect.fn() and refactored some usages to Effect.fnUntraced())
What is the feature you are proposing to solve the problem?
Effect.fnUntraced() should accept a { self: this } overload the same way that Effect.fn() does
What alternatives have you considered?
No response
What is the problem this feature would solve?
using
Effect.fnUntraced()to define class methods (when tracing is not needed)consistency with
Effect.fn()API (I ran into this when I realized I didn't needEffect.fn()and refactored some usages toEffect.fnUntraced())What is the feature you are proposing to solve the problem?
Effect.fnUntraced()should accept a{ self: this }overload the same way thatEffect.fn()doesWhat alternatives have you considered?
No response