Miss Dada  🏳️‍⚧️

especially since often it recommends to fix the "module does not have method f" error by including Kernel, which in my case breaks my program

but also it's just not necessary -- you cannot call a method from a module unless it's been included into a class, at which point Kernel is in scope

Unless it's included in a class which extends `BasicObject`

but that's statically decidable

if you're solving this problem at all you should be able to see that I'm only including module M into classes that descend from Object

Sure. Or at least be able to state "This module is only allowed to be included in classes that descend from Object"

sure but then you'd have traits

I don't think that's true. You just end up with a way of representing the contract of your module (and I'd assume it would error if you tried to include it in a class which doesn't follow that contract). Either way, "inherits from object" should be the default assumption IMO