We would like to understand extension functions a ...

# build-tools

[greenrobot]

We would like to understand extension functions a bit better. How does the compiler know they are available? We have a class transformer in place as part of our Gradle plugin, and after that step extensions functions raise compiler errors when used from another module. (Context: https://github.com/greenrobot/ObjectBox/issues/134)

[yole]

make sure you’re not corrupting Kotlin’s @Metadata annotations

[greenrobot]

That's the only source for the Kotlin compiler? The actual classes with extension functions should not be transformed, but just copied on a file level. So `@Metadata`should be untouched. Can you think of another reason?

[yole]

there are also .kotlin_module files, they should also be preserved

[greenrobot]

ah OK, will check