This warning was not present before the code was in a separate module. I guess it is an extra safeguard for implementation changes in modules by others which you expect the implementer knows when working in same module? Or is there an other reason?
➕ 2
g
gildor
04/10/2018, 7:30 AM
Yes, module can be updated, so you cannot be sure about nullability, it’s just jvm bytecode