https://kotlinlang.org logo
Join Slack
Powered by
this code doesn’t complain in compilation time but...
# announcements
e
this code doesn’t complain in compilation time but in runtime if I don’t specify the type of 
classLoaders: Array<out ClassLoader>?
when 
*classLoaders
is passed as parameter
Copy code
val classLoaders = reflections.configuration.classLoaders // Array<out ClassLoader>?
ReflectionUtils.forNames<Any>(reflections.allTypes, *classLoaders)
a
What does it say at runtime?
e
NPE
p
When you are interacting with platform code that has no Nullable annotations, Kotlin lets you decide whether the type is nullable or not and when you don’t do that it decides based on context.
In this case, you are using the 
*
operator which only works with non-null arrays
since your array appears to be null it throws a NPE
if you declared 
classLoaders: Array<out ClassLoader>?
you would’ve gotten a compilation error there instead
p
And this is why we should never promote Kotlin as a null-safe language because it's only as null-safe as it's platform i.e. not at all.
p
well, safety is relative. You can always do unsafe things like using platform types or casting, but outside of that you are pretty much safe.
Kotlin makes it harder to shoot yourself in the foot than Java, but you can never remove all of the foot-pointing guns. Even Haskell has 
System.IO.Unsafe
k
@poohbar as long as you stay withing Kotlin it's pretty much null-safe.
So "Kotlin is null safe" is true, but since Java is not of course calling Java code isn't either.
p
stay withing Kotlin
How many real-world projects can get away with not using Java?
e
actually 
reflections.configuration.classLoaders
is annotated with a 
@javax.annotation.Nullable
return type, I thought this could be inferred.
p
@Nonnull
is supported
@Nullable
isn’t
e
thank you @pavel
👍 1
a
@poohbar only use nullable types when interfacing with java and you have full null-safety
p
Since the compiler does not force you to do that it's like saying that Java is null-safe if you do a null check before accessing any reference.
a
at one point, kotlin did exactly that, but it was removed because a lot of developers were not happy with it
p
I know the history of Kotlin. And I also know that once this was removed Kotlin ceased to be a null-safe language and we should stop saying it is.
I am not saying I have a better solution though.
k
Kotlin is null-safe, the interaction with Java is not. Do you also say that Java is not memory safe because it can interact with the JNI?
2 Views
Open in Slack
PreviousNext
Powered by