but yeah, that opens up a different can of worms

I actually prefer your suggestion of removing the variable altogether

yeah, because in the most cases intent argument used only once to initilize real state of Activity. For example use some “state” field. Activity has different states depending on arguments, and just initilize it onCreate and let other parts of code work with clear non-nullable structures (even use Sealed classes for complicated cases, very clear and type safe)

Great. Thank you guys! All those are options, obviously. All might work in my case. Great reference for my learning process 🙂

What do you think about that? If my projID is null, I am fine if nothing happens in that case.

Looks good to me.

Please do not return in the middle of an expression. There are rumors about a kitten being killed each time you do so 😉 Use a local variable,

also

,

if

, etc. Unless you are one of those extremely-short-code-is-a-must fetishist, of course

Huh never heard of that one, in my opnion it often makes he code very readable.

agree, that local val would be better, but don’t see something very wrong here

I would rather have it like

val proj = Proj(projID ?: error("projID is null"))

Expressions are not for control flow

https://twitter.com/kotlin/status/913705698822950915 Kotlin 1.2 Beta is here! Welcome to try it and give us feedback: https://blog.jetbrains.com/kotlin/2017/09/kotlin-1-2-beta-is-out/ Twitter

Kotlin 1.2 Beta is out We’re happy to announce the Beta release for Kotlin 1.2. With this release, we’re unveiling the major new feature of Kotlin 1.2 – experimental support for multiplatform projects. Also, the language and standard library are now feature complete – all … Continue reading →

oh ok, didn’t know that

I’m not sure that everything has been released: http://dl.bintray.com/kotlin/kotlin-eap-1.2/org/jetbrains/kotlin/kotlin-compiler/

There is no 1.2-Beta version.

📣📣📣📣 Attention! This blogpost and tweet were accidentally published too early, and the release process for Kotlin 1.2 Beta has not been finished yet. Sorry for the inconvenience. We’re working on some technical issues now, and will post an update as soon as they are fixed.

Is there a changelog for 1.1.51? Nothing here: https://github.com/JetBrains/kotlin/blob/master/ChangeLog.md

Probably not, you're the second one to ask.

sorry, missed that

No problem, that's just why I think there is no changelog.

there is one here https://github.com/JetBrains/kotlin/releases/tag/v1.1.51

Ah that wasn't there yesterday ☺️.

Hi, I faced the situation when in Kotlin 1.1.51 kotlin classes does not compile to java classes explicitely. Is it possible to workaroud this?

What is the idiomatic/kotlin way to execute a closure after a delay?

"Attention! This blog post was accidentally published too early, and the release process for Kotlin 1.2 Beta has not been finished yet. Sorry for the inconvenience. We’re working on some technical issues now, and will post an update as soon as they are fixed."

rip

https://twitter.com/kotlin/status/913800092301365248 Kotlin 1.2 Beta is here! Welcome to try it and give us feedback: https://blog.jetbrains.com/kotlin/2017/09/kotlin-1-2-beta-is-out/ Twitter

You are sure? Still no 1.2-Beta version here: http://dl.bintray.com/kotlin/kotlin-eap-1.2/org/jetbrains/kotlin/kotlin-archetype-jvm/

I think it should say

1.2.0-beta-31

instead of

1.2-Beta

?