@yan: The idea is that maybe that release is bad, because there are odd errors with missing functions when using it (see above from Benny)

It’s the new release, built for 1025

@benny_wang: can you share with @yan the full error including any stack trace of the error, (add as a snippet here)

@apatrida: Ok, just wait a moment, I’m trying anko 0.8.2rc2 right now

ah, you hadn’t tried the newest yet? thought that was the earlier discussion. oh he updated it, I see.

Anko_startActivity_crash_after_upgrade_kotlin_to_eap-1025.txt

@yan I update anko to 0.8.2rc2, but Exception still here.

@benny_wang: Ok, can you show me the relevant part of code of that function?

StockFragment$stockDetail$2.invoke

(line 67)

@yan: ok val stockDetail: Command<Int> by bindCommand("stockDetail") { params, canExecute -> startActivity<StockDetailsActivity>("id" to stocks!![params].id) }

@yan: startActivity<StockDetailsActivity>("id" to stocks!![params].id) is the problem

H-m, will look into this. Thanks!

Intellij EAP 16 seemed to add Kotlin EAP as the default, or else something else caused my plugin in 16 to jump to EAP (maybe I was sleepwalking). This SO article seems to be the same, http://stackoverflow.com/questions/35168285/the-binary-version-of-its-metadata-is-1-0-1-expected-version-is-1-1-0 … therefore some people are using the Kotlin EAP without knowing.

and it doesn’t set the plugin update to EAP channel so those users will sit on 1017 (or whatever version was shipped) until next public release

@apatrida: yes, this was caused by an internal miscommunication

happens

as soon as the public RC is out, we’ll include it in the next IDEA 16 EAP

I'm getting this error when trying to use

rc-1025

Error:Could not find org.jetbrains.kotlin:kotlin-annotation-processing:1.0.0-rc-1025.

Is there something I've forgotten to do?

it looks like we didn’t publish kapt to the EAP repo

never mind @yole i'm stupid enough to add

maven { url '<http://dl.bintray.com/kotlin/kotlin-eap>' }

to

buildscript {repositories {}}

instead of

repositories {}

Please use

anko-common-0.8.2rc3

(3) when compiling using

rc-1025

When I want to override some method from Java AS/IJ generates stub method with nullable types - such as

override fun onCreateView(inflater: LayoutInflater?, container: ViewGroup?, savedInstanceState: Bundle?): View? {
        return super.onCreateView(inflater, container, savedInstanceState)
    }

before EAP it was possible to remove

?

and happily use not-null types from java. is it intentional that in eap such override is forbidden?

//note removed question marks
    override fun onCreateView(inflater: LayoutInflater, container: ViewGroup, savedInstanceState: Bundle): View {
        return super.onCreateView(inflater, container, savedInstanceState)
    }

with error: `Error:(115, 5) 'onCreateView' overrides nothing```

Kotlin now understands Android nullability annotations

so if a parameter is annotated as

@Nullable

in the Java class, you have to use correct nullability when you implement it in Kotlin

container

and

savedInstanceState

are actually nullable, only

inflater: LayoutInflater?

can be safely replaced with

inflater: LayoutInflater

@yole: is there any reason why you match against the fully qualified name for annotations vs just seeing if it’s named Nullable/NotNull/NonNull?

it's awesome Kotlin understands now these annotations - few bugs less

different annotations have different semantics

for example the Bean Validation annotations have a significantly different meaning even though they use the same names

@yole: well I figured something called NonNull or Nullable would be pretty straightforward 😕 Nevertheless, Kotlin made the right choice baking it into the type system directly

where's the list of annotations maintained?