# Proper nullability for built in Java classes?

**URL:** <https://discuss.kotlinlang.org/t/proper-nullability-for-built-in-java-classes/5122>\
**Category:** Language Design\
**Created:** [October 26, 2017, 3:06pm UTC](https://discuss.kotlinlang.org/t/proper-nullability-for-built-in-java-classes/5122 "2017-10-26T15:06:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sxtanna](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.kotlinlang.org/sxtanna/32/4134_2.png) [@Sxtanna](https://discuss.kotlinlang.org/u/Sxtanna)\
**Post date:** [October 26, 2017, 3:06pm UTC](https://discuss.kotlinlang.org/t/proper-nullability-for-built-in-java-classes/5122/1 "2017-10-26T15:06:50Z")

</div>

I noticed when invoking methods like

[AnnotatedElement#getAnnotation(class: Class)](https://docs.oracle.com/javase/8/docs/api/java/lang/reflect/AnnotatedElement.html#getAnnotation-java.lang.Class-)

The values are not marked as explicitly nullable.  
Would it be possible to remove the ambiguity of the input and return types since they are built in classes?
