Right, so just write those in

gli

and call the appropriate actual library methods?

And the implemetation would be in

interface load

? That's a really strange design ☺️

it's the current way I found to keep methods in separated files but available under the same

object

One option is to make them package-level methods, you can split those over multiple files quite easily. I think the only other option is to make a base class for all of the properties and use extension functions to split the function over multiple files.

I also took in consideration the package-level options, but it doesn't play so nice as kotlin with java