Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@ScriptCoded How is it like in Python?
-
@gitpush more readable
x = z if a != b else y -
@vane well this assuming all vars are called a b c d e ...etc.
Imagine a veryLongVarNameForNoDamnReasonWeAllSawSuchNamesAndDroveUsCrazy
Personally, I wouldn't want to imagine a long var name lol -
@gitpush we don’t do java naming here, variables are named very_long_variable_name and there is line length limit in pep8 so we can focus on solving problems not creating new ones except python 2 to 3 of course :)
-
@vane good point. Let's hope I get to know why Kotlin has this lol
-
@gitpush I think you can skip braces like in javascript so it can be more nice
var x = if (a != b) y else z -
@vane Yes we can, and it looks better like that tbh
-
@gitpush yeah those new languages look all the same right now:
kotlin, swift, go, scala, es6 js
differences are cosmetic -
@gitpush Your example only works with var, but one may want to use val to ensure it can't be reassigned.
-
@vane lool trying to keep up with JS frameworks I see
-
If you find an if expression less readable than an if statement, your brain is too ingrained in procedural programming. Work with any (even halfway) functional programming language for a while, and you will not want to miss the if expression anymore.
And yes, the if expression is equivalent to the ternary operator expression in C/C++/C#/Java.
Related Rants
Lol @ Jetbrains
( ͡° ͜ʖ ͡°)
Can someone please explain the benefits of this in Kotlin:
var x = if(a !=b) {
z
}else{
y
}
Even for a conditions with one line body it looks bad in reading and getting a clue of what does this do.
I mean whats wrong with:
var x: MyObject
if(a!=b){
x = y
}else{
x = z
}
Even in switch cases (or as kotlin calls: when) True one return source, but now good luck finding the last line that is the actual returned value ...
random
kotlin
not sure why