📦 Separation of artifacts

[LVMVRQUXL]

🤔 The problem

For now, when users depend on Kotools Types, they import all types provided by the library.
But what if they only need explicit types representing numbers?
Currently, it is impossible to benefit from the type-system of Kotools Types while being selective on which type users decide to use or not.

💡 The idea

Like suggested by the Kotlin community on Reddit, the idea is to separate this library in multiple tiny ones for improving the user experience by allowing users to import only what they need.

For instance, instead of importing all types by depending on org.kotools:types, they can import only numeric types by depending on org.kotools:numbers or org.kotools:numeric-types.

🙏 Help needed

Please give this post a reaction if you are interested in this change and comment below your thoughts on it.
Also, if you have any idea for naming these new artifacts, feel free to suggest them in the comments section below.
We would love to have your feedback!

[LVMVRQUXL]

For now, because serializing types using Kotlin Serialization is an optional functionality of Kotools Types, we have only separated this functionality (through the types-kotlinx-serialization subproject) from core types. Maybe in the future it will be interesting to split more the library, but not for now, as it could increase its management complexity for no real benefit.