Post

Scientists, could, should, etc. etc...

That's one of my favorite things about Kotlin.

I would assume so, given that without the inline modifier you cannot use statements like return to return the outer function from within the lambda

I see, so its some kind of carrier grade optimization technique?

I'm going to use this if you don't mind.

Not trying to tempt you, was just curious xD I know how this type of thing goes, trust me xD

Every other language basically tries to reinvent LISP, sooner or later.

Funky

Forty years spent trying to understand and fix other peoples' code, in a variety of languages, tells me that this is probably evil.

While it certainly looks neat, tricks like this make the code less readable by both humans and automated tools. I would not use this or similar patterns in production code.

Huh?

Ah yes you are right. Tools working at the kotlin source level seem to work fine. This leaves inconveniences only for runtime tools (debuggers, coverage, profiling), but nearly never visible in practice. My bad. Too much C and Lisp in my young years :-)

Will Kotlin still be around in 10 years' time?

Sure, when you put it THAT way!

JavaScript:

Interesting—I find `a + b` a lot more readable than `a.plus(b)`, but different strokes for different folks.

Yup, this was what I thought - i immediately thought "i could do this exact thing in python or rust but the brackets might be in a different place"

Huh, neat. That block syntax for lambda/closure expressions reminds me of Swift (which, to be clear, I absolutely detest as a language but I do think it has some good parts)

.Net does crap like that, but I don't know how free it is.

(Or, for that matter, maybe the function supports some kind of currying in general and blocks can be implicitly converted to lambdas -- there's not enough context in this code snippet to infer exactly how it works.)

Call by name has reappeared in functional languages though I’m not sure if in the same form. I mentioned it as a concept of peripheral interest while we’re on the subject of alternative methods of parameter passing,

... Or text replace, or something...

Can it be useful in real project though?

You could also implement "if" and "while" as higher order functions like this. I'd say that's control flow. But is it "control flow altering"? Idk, that phrasing sounds confused.

kotlin is ruby? (the ruby syntax is “yield” to blocks)

One of the main reasons that Java was successful, back in the day, was that (unlike C++) it did not allow exactly this: the creation of new languages. When you got code back from some offshore contractor, there was a fighting chance you could at least read it