OliverO2

Results 187 comments of OliverO2

OK, in that case I'd prefer `withPermutations { ... }` to indicate that it influences the behavior of the code inside (like `withContext`) and does not return any meaningful value...

> You mean make proptest just an extension on test scope? No, I was actually thinking of abandoning `proptest` and making `TestScope` absorb `proptest`'s scope. > Would still need some...

Looks really cool now, I'd expect the new syntax and integration to significantly ease onboarding! Just one minor remark: Since we're potentially running _lots_ of permutations, I'd favor the plural...

Valid arguments. Each naming variant captures part of what's going on. I wasn't even aware that `before`/`after` apply to each permutation, although that makes the most sense. Still, naming helps...

Thanks! Looks like a [change in the Kotlin compiler](https://github.com/JetBrains/kotlin/commit/7f6562285b6b228e435550e1a0a5a12fbab9a6cb) that requires updating the Kotest compiler plugin. ``` e: java.lang.IncompatibleClassChangeError: Found class org.jetbrains.kotlin.ir.declarations.IrFactory, but interface was expected at io.kotest.framework.multiplatform.embeddablecompiler.NativeTransformer.generateLauncher(NativeTransformer.kt:46) at io.kotest.framework.multiplatform.embeddablecompiler.Transformer.visitModuleFragment(Transformer.kt:65)...

Gradle needs a special setup to access snapshot artifacts. This is what I'm using to access the snapshots repo for the Kotest Gradle plugin: In `settings.gradle.kts`: ```kotlin @Suppress("UnstableApiUsage") dependencyResolutionManagement {...

Thanks for the feedback! Happy to hear that we have arrived at a viable solution. Kotest 6.0 development is pretty dynamic with no release date in sight, so sticking to...

I can't help with company policy, but for those still looking how to make this work: Have you tried to use the exact configuration I [posted above](https://github.com/kotest/kotest/issues/4177#issuecomment-2332391540)?

I don't do releases, so I'm not the one to decide how to proceed. What I can tell is: * This is not a "fix" that could be "backported". It...

On first glance there seem to be some antipatterns here (e.g. implicit use of `GlobalScope`, `async {}.await()`). Give me a day or two for a thorough review.