I ran into an issue with
Typeable not being in scope and found out
Typeable doesn’t really work on composite types.
This got me thinking, if type testing like the code linked in the issue here: Typeable instance not being discovered on generic type typetest · Issue #12668 · lampepfl/dotty · GitHub
should be a compiler error by default?
Type erasure whilst powerful can be of surprise in cases like this to newcomers to the scala language without knowledge of JVM internals and considering how easy it is to create code as such, wouldn’t it be reasonable choice to create a compiler error if no implicit
Typeable is found in scope instead of compiler warning?