I don't need and want any optional there

# announcements

[pp.amorim]

I don't need and want any optional there

[diesieben07]

You don't have an "optional". The parameter is not optional. All that the intrinsic check does is make the error message explicit ("parameter X was not expected to be null") instead of a blank NullPointerException.

There is no added value in forcing the compiler to remove this check.

[pp.amorim]

I don't want to apply this rule on my entire project 😞

[pp.amorim]

I wish I could use an annotation to tell the compiler to not add these checks on this specific function or class.

[diesieben07]

Why?

[pp.amorim]

because my project is big? I don't want to remove all these checks just because a single function is using it.

[diesieben07]

I mean, why do you not want these checks?

[SiebelsTim]

Write the function in java 😛

[pp.amorim]

omg no

[pp.amorim]

I don't understand why FloatArray needs to be checked if it is only called by Kotlin sources.

[diesieben07]

1. The compiler cannot verify that it's only called by Kotlin
2. Separate compilation makes it so that you have no guarantees on what you will be called with.

[pp.amorim]

that's understandable, couldn't a annotation tell the compiler to not accept this method of being called from a Java code and not include these checks?

[diesieben07]

Java sources are compiled by javac, not kotlinc. Kotlin has no influence on what happens in Java.

[SiebelsTim]

In theory it could omit the check by an annotation, sure. But the compiler has no such support. Probably because there is no evidence that the Intrinsics.* call has non-negligible impact on the performance.

[pp.amorim]

yes, the Kotlin linter can make the function not available in Java, I am very ignorant on this subject matter

[diesieben07]

What does the linter have to do with it? I am not sure I follow. And yes, the performance impact is likely negligible. The static method is almost guaranteed to be inlined by the JVM and then the JVM will eliminate any null checks it would otherwise insert by itself.
So in the end you get pretty much the same machine code, except you now have a meaningful error message.