quickstep24

``` inline fun Unsafe.css(@Language("CSS")css: String) = raw(css.trimIndent()) ```

> I would like to pitch for some random sampling methods such as > > ``` > fun List.sampleRandom(random: Random = DefaultRandom): E > fun List.sampleRandomList(size: Int, random: Random =...

> The first one is incorrect because its slow and possibly non-terminating. > > When sample size is close to list length `(n)` I believe the program has an expected(in...

@altavir @fvasco This is not a contradiction to me. I would say "double-bang types" should also be avoided and only be used under very specific conditions. The KEEP states there...

> fun foo(t: T?, tn: T) > > fun foo(t: T, tn: T?) > > fun foo(t: T?, tn: T?) > > fun foo(t: T, tn: T) Yes, of course....

> One developer might prefer this: > > 1. If `suspend` -> make italic > 2. If `composable` -> make red > `Code Coloring` is a metaphore. It does not...

Did you mean to write `value class B(var c: Int, var d: Int)`?

Personally, I would prefer a DSL syntax within regular Kotlin over a new "logic" syntax (expressiveness over conciseness). I believe this does not have to be ugly. The performance benefits...

First of all, I really appreciate the introduction of named context parameters. I am still trying to realize the other changes. As I understand, the `context` modifier now serves two...

> It's even debatable whether `Logger` is a good example of context receiver, and shouldn't just be a named context parameter. In that case, the regular declaration suffices, no need...