A modern programming language that makes developers happier.

kotlinlang

image.png

I mean, any `public`  declarations in `test`  module are already encapsulated, simply because they are in tests

Then it doesn't hurt to mark those `internal`

but... can't the Kotlin compiler consider any `public`  declaration in tests as `internal` ?

I think I have an idea for a compiler plugin

Actually, I saw someone marking test classes as `internal`

IMO it's easier if everything is consistent, so I don't mind the extra `internal` declarations in tests when necessary, as long as everything behave the same. But I can see why people would find some benefits in having this implicit `internal` by default for tests

Well, actually test modules can depend on other test modules
So I don't see any difference between main and test modules in terms of `internal` visibility

Well, is there any way to apply `test`  module for Explicit API Kotlin compiler feature? :grin:

figured it out:
```...
freeCompilerArgs = listOf("...", "-Xexplicit-api=strict")
...```


Does the Kotlin compiler even know that it's compiling a test module?

Maybe the Kotlin plugin runs compilation for each module separately

&gt; Does the Kotlin compiler even know that it's compiling a test module?
No, it doesn't
&gt; Maybe the Kotlin plugin runs compilation for each module separately
Yes it is. There is no difference for compiler between main and test modules
The only difference on the build system side, which marks main module as friend for test one, which allows to use `internal` declarations from main in test