2 ms·
If the first or second example would cause compiler error, it means that you would need to annotate every library usage. Your code will be full of casts on almo
by vbezhenar 2y ago
If the first or second example would cause compiler error, it means that you would need to annotate every library usage. Your code will be full of casts on almost every line, until the given library would migrate to null types, if ever. It makes no sense.
For example they explicitly saying that standard library will not migrate to null types, at least for now.
- jayd16 2y agoYou can still work with the nullable types, as is, from these libraries. You only need to cast/check when you want to use the non-nullability feature.