Hm it seems that this is not enforced by the compiler like a normal nullable declaration which means someone could use them without optional chaining and someone with in the same file. It confuses the code reader and it allowes possible null pointer exceptions bypassing kotlin null safety features