Split korge-foundation and korge-core in submodules

[soywiz]

Like the old libs, but for package name. Keeping korge-foundation and korge-core as a module without code linking to each module individually.

• korge-time
• korge-crypto
• korge-datastructure
• ...

So everything works as before but people can get the libraries segmented to what they need.

[soywiz]

Do this after merging / discarding PRs to avoid conflicts.

[soywiz]

I won't have time for this in the shorterm. If someone wants to contribute here, PRs are welcome.

• korge-datastructure is already picked by holloszaboakos

If someone wants to contribute in this split with PRs, feel free to do so. You can put a comment here to avoid other people to doing the same work.

[holloszaboakos]

We have a problem with circular dependency. We might have to do a bigger refactor than just separating the packages into modules

[holloszaboakos]

The math and the logger modules use the korlibs-datastructure, therefor we have circular dependency of gradle tasks and this problem is not solvable without gradle changes

[soywiz]

@holloszaboakos it should be fine:

Just add commonMainApi(project(":korlibs-datastructure")) in korge-foundation/build.gradle.kts so the math and logger packages have access to it.

If something from other package is required into datastructure, just copy that functionality into an internal package and provide those functions/classes as internal so they are not exposed.

When logger and math are split into modules, they can just depend on korlibs-datastructure. And if it just uses a couple of functions, then we can do the same: copy them as internal functionality.

[holloszaboakos]

That doesn't solve circular dependency problem (korlibs-datastructure also needs dependency for foundation). However as we already discussed on discord, we can duplicate code and make that internal.