We are excited to share a <https://github.com/Kotl...

# language-proposals

[bnorm]

We are excited to share a KEEP for Power-Assert! We're tackling long-standing problems with Power-Assert, trying to improve the out-of-the-box experience. And we're doing that by providing ways to directly integrate with the compiler plugin and APIs for call-site information. Let us know your thoughts!

[Oliver.O]

I'm currently investigating some edge cases with Gradle projects that would probably require explicit Power-Assert source set configurations for tests (just a hypothesis, I haven't done the necessary testing yet). TestBalloon autoconfigures itself for many scenarios and I wonder if Power-Assert should extend its defaults to automatically cover all source sets in test-only projects established via specific Gradle plugins as well.

[bnorm]

There are definitely plenty of Gradle improvements we'd like to make when it comes to Power-Assert, but these are outside the scope of the KEEP. For example, we want to make it easier to configure the source sets without having to define all of them explicitly. And there are probably other improvements as well. So if you have ideas, please open a YouTrack ticket for them, and we'll take a look!