`String.t()` is not properly picked up as typename inside map syntax
Qqwy opened this issue · comments
Turns out this only happens in modules that are part of the TypeCheck repo itself, as they would sometimes be compiled before TypeCheck's default override modules were compiled.
By using require TypeCheck.DefaultOverrides
we make sure that such a module is still compiled only after TypeCheck itself is recompiled with its own checks.
This does not impact any user code using this library in any way.
The fix is part of the now-published release v0.12.4.