Following up the conversation above about string c...

# codingconventions

[Dmitry Kandalov]

Following up the conversation above about string concatenation formatting, I tried using + on new lines as @gabrielfv suggested:

foo("one"
    + "two"
    + "three")

only to find that it doesn’t work with return, e.g. the following doesn’t compile because of + on new line:

fun bar(): String {
    return "one;"
        + "two;"
        + "three"
}

I’d argue this means that + and .plus() are already different enough to have different formatting 🙂 /cc @kevinmost

[gabrielfv]

So Kotlin compiler takes identation as a parameter to parse operations?

[kevinmost]

no, you have to put the + at the end of the previous line, not the start of the newline, for it to pick Foo.plus(Bar) over unaryPlus(Bar)

[gabrielfv]

Got it, although it kinda doesn't comply with the ?. scenario. Of course there's a good explanation.

[gabrielfv]

What are the applications of unaryPlus(), since unaryPlus(a) == a?

[kevinmost]

Yeah, it's a little weird. Maybe just to keep consistency with unaryMinus(), since you'd certainly want to do -50 for example 😆

[kevinmost]

it could have potential to be used in a DSL as a sort of alias for "add"

dependencies {
  + "org.jetbrains.kotlin:kotlin-stdlib:1.1.4-2"
}

[gabrielfv]

Well, the return case is understandable, since return "one;" is a closed statement, and so are the + "etc" lines, that cannot be reached and break compilation.

[gabrielfv]

So this constrains that convention