Miss Dada  🏳️‍⚧️

that, by itself, is a really interesting ergonomic result to me: rust is extremely restrictive, but when it won't compile, I feel like I understand why ruby is incredibly forgiving, so I'm sure my codebase contains bugs, but everything sorbet is telling me about is noise

saying that, I'm only getting my codebase from `false` to `true` type checking, not `strict` or `strong` but the things it's complaining about at `true` are artificially restrictive already

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"