Hiding internals from Java

[LVMVRQUXL]

🤔 The problem

At compile-time for the JVM platform, Kotlin transform the internal keyword to public.
This makes our internal declarations available for Java users who can misuse the API.

💡 The idea

The idea is to restructure the current project in the following modules:

• internal containing code that should be only accessible in Kotools Types modules
• library depending on internal and corresponding to the source code of Kotools Types publicly available.

For declarations that could be marked with the JvmSynthetic annotation, we will

The principle behind this change is the following:

• if the internal declaration is a property or a function, marking it with the JvmSynthetic annotation is enough
• in other cases, move it to the internal module.

This important change will hide effectively internals from Java.

✅ Checklist

Here's the checklist to address for implementing this idea:

• New internal Gradle subproject #299
• New library module #300
• New delivery workflow for library module #301
• Moving source code to library module #302
• Hiding internals from Java #303

🙏 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]

We've tested this idea by starting implementing the issues #234 and #254.

[LVMVRQUXL]

It is not necessary to introduce a library Gradle subproject for depending on another one: the commit 9052e77 adds a dependency from the root project to the internal subproject.