💥 Type system changes for Int numbers

[LVMVRQUXL]

🤔 The problem

The current type system for integer numbers represented by the Int number have 2 main flaws:

1. it gives an AnyInt type which is essentially a duplicate of the Int type already provided by the Kotlin standard library
2. implementations of AnyInt are comparable with other AnyInt by default, meaning that you can compare two ZeroInt, which is weird thing to do...

// The following shouldn't be possible.
println(ZeroInt > ZeroInt) // false

💡 The idea

The idea is to flatten the type system for Int numbers by replacing the AnyInt type by a new ConvertibleToInt type, and by removing the inheritance between actual types.
This change allows better precision in the API and eases the understanding of numeric types.

/** Types inheriting from this interface are convertible to [Int]. */
interface ConvertibleToInt {
    fun toInt(): Int
}

interface NonZeroInt : Comparable<NonZeroInt>, ConvertibleToInt
interface PositiveInt : Comparable<PositiveInt>, ConvertibleToInt
interface NegativeInt : Comparable<NegativeInt>, ConvertibleToInt
interface StrictlyPositiveInt : Comparable<StrictlyPositiveInt>, ConvertibleToInt
interface StrictlyNegativeInt : Comparable<StrictlyNegativeInt>, ConvertibleToInt

🙏 Help needed

Please give this post a reaction if you are interested in this change and comment below your thoughts on it.
We would love to have your feedback!

[LVMVRQUXL]

There is an interesting article by IBM on flattening inheritance.