Ivan “CLOVIS” Canet

This problem still seems relevant. Here are two builds of the same dockerfile: - [Without workaround](https://gitlab.com/opensavvy/automation/containers/-/jobs/8287003602), timeout after 60 minutes - [With workaround](https://gitlab.com/opensavvy/automation/containers/-/jobs/8335028909), done in 5 minutes

I'm writing [a test framework](https://opensavvy.gitlab.io/groundwork/prepared/docs/) that allows declaring tests declaratively. This is particularly convenient because it is a proper Kotlin DSL with no magic, which makes it much easier to...

I took inspiration from other tests, which seem to use `expect(Int)` and `finish(Int)`, but I'm not completely sure what they're for nor how to use them, so I didn't. Please...

I would love to, but sadly my schedule doesn't allow me too… Feel free to make the changes you want if I'm too slow :)

This looks very good! > A special note about Kotlin/Native: currently, Kotlin/Native has a completely separated distribution that is to be supplied by a build system. It can be bundled...

Thanks, this does seem to work!

Hey, KtMongo author here. I'll give a bit more context. KtMongo relies on KotlinX.Serialization to convert Kotlin types to and from MongoDB BSON. Through this, we support `sealed class` and...

> > As to "not having to resort to `when` matches" you can use a calculated property: > > @Serializable > abstract class Base { > abstract val type: String...

> Why not have something like: > > User::foo.isInstance() In theory, that would be the best option, yes. But it cannot be implemented due to KotlinX.Serialization being magic: - We...

Sorry, this explanation is quite abstract and I'm not sure I'm following everything. To make it a bit more concrete, how would you implement the following? ```kotlin @Serializable class User(...