Nikita Shilnikov

Excuse my ignorance but what is "concern module pattern"? :) Why is this patch needed? At first glance, I don't feel comfortable with having a workaround for a misused ruby...

or use effects... Though, for effects you'll also need a handler somewhere so setup a bit more involved

I won't go into details right now, but I want to note that this is strategy-dependent. For example, effect-based DI works with modules or whatever. And I believe we can...

How would it work, though? Implementation-wise I mean.

But this would break the assumption an object is fully initialized after `.new` call. Normally, I don't mutate objects meaning I call `.freeze` after initialization. Your suggestion will break in...

Freezing is not about the cost actually. It's a technique of separating boot time from runtime. An application stack and its constituents are meant to be immutable, hence frozen. Anyway,...

you should all just use effects and call it a day 😆

@solnic I don't have preferences over injection strategies. In this case, it looks strange that in order to inject a dep you'll get an anonymous copy of a class. I...

@candland https://dry-rb.org/gems/dry-effects/0.1/effects/resolve/ I also have a sample project with dry-everything https://github.com/flash-gordon/rt-tracker And there's an example of using effects in an existing rails project https://github.com/flash-gordon/forem

@maxhollmann there's no out-of-the-box solution I would say, I'm still gathering use cases to wrap them with a nice API. Normally, I create a single effect stack and re-use it...