That applies only to the Mox strategy. The library itself provides dependency resolution and injection functionality, independently of Mox.
Yes. I’m considering one based on naming conventions. Other ideas are definitely welcome.
I’m not entirely sure I understand. Could you elaborate a bit more on this?
Good point, thanks for catching that. I’ll fix it as soon as possible.
As for the macro name, I like inject, but I want to think a bit more about this.


















