Jonathan Cornaz

>Another option is to create separate Gradle source sets and corresponding test tasks. This has the advantage of allowing you to have different dependencies for each type of test (which...

>Looks like the bug was in gradle-testsets-plugin, can I close this issue now? There was indeed a problem in `gradle-testsets-plugin`. Many thanks to @tkrullmann for solving it. However, if I'm...

That's a quite different than #566. #566 was about an exception thrown during the discovery phase, and that's definitely fixed. Your issue is about forgetting to add the test runner....

>Is AutoCloseable available in the multiplatform stdlib? No :-( However, I don't think it means that we cannot support it at all. There could be either: * A specific implementation...

Thanks @raniejade. It is kind of strange because I don't see the error @looserkevin do (we work together on the same codebase). However, if I manually look at https://repo1.maven.org/maven2/org/spekframework/spek2/spek-dsl-jvm/2.0.17/spek-dsl-jvm-2.0.17.module I...

As the PR for 'eager evaluation of memoized ' has been closed (#661). Maybe memoized could be made thread safe in the mean time?

Actually, after playing a little bit, I think using `disposableEffect` to start a long running job that fire messages is not so bad. Maybe all we need is only documentation...

Personally I create the following simple helpers: ```kotlin fun Effect.asFlow(): Flow = channelFlow { this@asFlow { sendBlocking(it) } } suspend fun Effect.perform(): List = asFlow().toList() ``` And then in my...

> Caches will all expire eventually so I don’t think being able to clear specific ones is going to be very useful. Please consider the following use case: A gradle...

@laim2003 why is that marked with "question"? What is the solution of this problem?