There's plenty of use-cases for it in oss. For example trying to avoid polluting consumer's namespace with unnecessary api that have nothing to do with your lib and are just used internally at the implementation layer.
My rule of thumb for this is to always use implementation dependencies by default and switch it to api dependency if any part of it appears in my public api.
a
altavir
02/18/2023, 6:58 PM
oops
altavir
02/18/2023, 6:58 PM
wrong thread
b
Big Chungus
02/18/2023, 6:58 PM
Figured 😀
a
altavir
02/18/2023, 6:58 PM
sorry
b
Big Chungus
02/18/2023, 6:58 PM
Now I'm curious for the context!
a
altavir
02/18/2023, 6:59 PM
Just a private discussion about how dependency resolution works. There was a thread on the right, but I did not notice that the wrong channel on the right.