Anyone know how to achieve kotlin-like `inline` be...

# random

[Youssef Shoaib [MOD]]

Anyone know how to achieve kotlin-like inline behaviour in Scala? Does something like this just work?

inline def forEach(inline block: Int => Unit): Unit

With block getting mentioned only once inside

[ephemient]

https://youtrack.jetbrains.com/issue/KT-6456/Support-lazy-function-parameters like this?

[Youssef Shoaib [MOD]]

I mean the other way around. I want to write efficient map s for instance in Scala, or a for-each, but without a closure actually being creates

[ephemient]

assert is hard-wired in the compiler to be lazy in its argument but otherwise there isn't

[ephemient]

why though?

[ephemient]

oh wait you're asking a different question than I thought

[Youssef Shoaib [MOD]]

Mostly as an academic exercise. I want to use such code while still being able to argue that it's efficient enough. inline gives me that in Kotlin, so I'm hoping that there's an equivalent in Scala, and figured if anyone would know it would be people here

[ephemient]

Scala 3 did add https://docs.scala-lang.org/scala3/reference/metaprogramming/inline.html

[Youssef Shoaib [MOD]]

Yeah so would the following code do the trick, or do I need some complicated Quotes stuff?

inline def forEach(inline block: Int => Unit): Unit

Also I'm guessing there's no nice (and performant) way to do non-local returns, so I would likely need to have block return whether to keep iterating or not

[ephemient]

yeah I'm not sure from their docs

[Klitos Kyriacou]

assert is hard-wired in the compiler to be lazy in its argument

That's only in Java, not in Kotlin.

[ephemient]

it is in kotlin, the assert function is special. https://youtrack.jetbrains.com/issue/KT-7540/Do-not-evaluate-the-argument-of-assert-when-assertions-are-disabled-on-JVM

[Klitos Kyriacou]

That's strange, I'm using 1.9.22 and the following prints "AB":

fun main(args: Array<String>) {
    assert(false.also { print("A") } )
    println("B")
}

[ephemient]

ah, -Xassertions=jvm isn't default, but it is the default (only) behavior on native and js