Earlier quoted context omitted.
Are we, though? No offence but if an external module starts calling an internal function they better prepare a PR that changes the internal (yes, I know, by convention) to a public one. This is a signal to the developers of that module that they have to maintain the behavior. That PR might well be rejected. And you have to work with the module owners to get your case supported. Anything else is not responsible and I…
or they could just test and maintain the hack on their own.
Yeah, good luck with that. I've had too many libraries change underneath me by clearly violating the previous contract that I know it doesn't work.