thanks, i realize that you can pass around functions but if we’re building a dependency root which has services that model behaviors, they usually come as “bunch of functions” rather than a single one (e.g., imagine a repository, which will likely always have a get and a set built on the same persistence layer).
i think my question is more along the lines of “how do you provide and pass around interfaces” (think hexagonal architecture)