You are currently viewing How to structure a non-object-oriented project in Kotlin?

How to structure a non-object-oriented project in Kotlin?

I have heard that object-orientation is not necessarily the best way to design Kotlin projects. But I can’t find any good resources to learn the overall architecture that one would use instead. I understand that top-level scope may be involved.. but I have questions about how namespaces are organized, and name collisions are avoided, module interfaces are kept clean and free of excess coupling, etc. Can anyone point me to some guides or introductions to this style of code organization?

submitted by /u/sacheie
[link] [comments]