Ivan “CLOVIS” Canet

@apatrida if your project is open source, please [create an issue describing it and giving the download link](https://gitlab.com/opensavvy/automation/kotlin-vite/-/issues/new), I'll make it into an official sample for the Vite plugin so...

Personally I'm in favor of `BigInt`. I think it's well established in most programming languages that fixed-sized numbers have a simple name and dynamic-sized numbers are prefixed with `Big`. I...

The intended usage is: ```kotlin context("group") { parameterize { val x by parameter(...) // ... test("test") { // suspends with `context`'s coroutine scope, through parameterize's } val y by parameter(...)...

Do you know if this problem also applies to Dokka v2?

Uh. That's strange, because I'm still seeing #170 with the latest Dokkatoo version. Once I migrate to Dokka v2, I'll recreate the issue there.

In this example, would `B` be marked as unused? ```kotlin fun foo(): Unit = try { ... } finally { B } ``` I very often see this pattern, where...

> Therefore, we do not plan to address this problem in the current design stage. let, and some other functions will be marked as @IgnorableReturnValue to avoid a large number...

> When this feature becomes stable, state 2 will be the default. Therefore, all Kotlin users would immediately benefit from every library that is correctly annotated without additional configuration. I...

I understand why this proposal doesn't apply to regular properties, but I think it potentially should apply to `provideDelegate`. Multiple DSLs use `provideDelegate` to access the property name as some...

> @kyay10 said: > Maybe, in the future, state 3 can be the default if someone has explicitApi turned on? Maybe, but I don't think that's enough. I'm thinking of...