You mean like in C++ where the Enum type name is not needed when the context makes clear what it is (without poluting the namespace like C style enums do)? I can see where not writing the enum type name is useful, but I would say introducing a separate type for that is unneeded (regular Kotlin enums are not integers in disguise - like C enums), it could just be a change in the language grammar (with appropriate ambiguity/priority rules).