MarsGoatz

I would go for something that explicitly suggests that nullable objects aren't allowed and make it agnostic of business logic, e.g., user strings or server side strings. In the end...

> tagged strings. This is pretty cool! Thanks for the share, learning something new everyday. I would go with `nonnull` maybe, more explicit or `nonnullable`. This sounds so much like...

Representing nullable value as non nullable using `late` keyword sounds like a hack to me. IMO, You use `late` keyword when you are sure the object will never be null...

>This would be very inconvenient: print and log statements are too common. The simplest fix would be: no tags; introduce a special escape symbol for nullable values. E,g, "$\foo" (which...

@rakudrama I understand the point you are making and I appreciate the examples. So, as a Dart user via Flutter, with null safety feature, I am thinking that Dart forces...

> I think everybody understands the problem now (your original post was too abstract, hence the confusion). I think as an end user of Dart, I look at different things...