I want to execute two functions on the same line w...

# getting-started

[Ray Rahke]

I want to execute two functions on the same line within a conditional block without using curly braces.

Untitled.kt

[Ray Rahke]

This results in the unintended behavior of c() always being executed as the ; breaks it outside of the else, despite them being on the same line.

[Ray Rahke]

are there any alternatives. I thought of doing

else
    b() && c()

but this only works for boolean functions

[Casey Brooks]

Yes, this is correct. Kotlin doesn’t have significant whitespace like other languages, so there’s no inherent relation between two statements on the same line.

The important bit is the statement, not the line. An if/else block without curly braces evaluates the next statement for the conditional, not the next line

[Ray Rahke]

Was just wondering if there were any syntactical tricks i could use to get this to work

[Ray Rahke]

I know it is a weird want but I am really really fond of braceless, singleline if statements.

[Casey Brooks]

Just throw braces around the lines (you can do it on the else without needing them on if)

if (condition)
    a()
else
    { b(); c() }

[Ray Rahke]

else
_b_(), c()

comma doesn't work 😕

[Ray Rahke]

heh yeah, but at that point I might as well do a normal braced else

[Ray Rahke]

well

[Ray Rahke]

it doesnt take up the last line so that is better I guess

[Ray Rahke]

thanks

[ephemient]

in principle you could

fun run(vararg blocks: () -> Unit) {
    for (block in blocks) block()
}
if (condition) a() else run(::b, ::c)

[ephemient]

but your initial code is already not common Kotlin style as far as I've seen, which is that multiline always uses braces

[Ray Rahke]

yeah. i just think when the executions are quite short it is easier on the eyes to have them horizontally adjacent on one line

[Ray Rahke]

and then the braces just add visual noise since it's only 1 line long

[Ray Rahke]

not a big deal

[Jeff Lockhart]

You might reconsider your aversion to curly braces when you consider the potentially serious consequences of such a bug that's easy to introduce by not using them. It makes the scope explicit when using multiple lines.

[ephemient]

also I would recommend avoiding lines that start with a bare {, because of how easily that could be interpreted as a lambda in Kotlin