Someone wrote a detailed analysis of why it was not easy to extend C# to support not-null, ie, print (string! msg), anyone have a link?
-
@jsonmez Unless it's guaranteed not to be null, i.e. I can see how you can get away with it in F# since guarantees are baked into the lang.
@demisbellot It does all circle back to @migueldeicaza 's initial query. If we could eliminate null in C#, then things are much better IMO.
-
-
@jsonmez Definitely not a fan of removing them, there's useful stuff like optional params + complex object requests that would be hard w/o. -
@demisbellot Well I certainly could be wrong. I often am, just my opinion at the time. :) - 2 more replies
New conversation -
-
-
@jsonmez Though I would welcome adding a non-null construct like T! and an existential operator like: custom?.address?.postCode -
@demisbellot Yeah, I agree I would settle for that. Would simplify much code.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.