The #CSharp language has this `default` keyword which breaks parametricity. It has no redeeming benefits. It is awful.
-
-
Replying to @davetchepak
@davetchepak@dibblego Unfortunately the "default" keyword seems to be a necessary evil... not sure why they split type params in refs/value1 reply 0 retweets 0 likes -
Replying to @mausch
@mausch@davetchepak Is it really? If I delete it, am I worse off? All I need is a first-class var (ST), then I am good to go innit?1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@davetchepak Yes, but I meant in the context of the current .NET type system.1 reply 0 retweets 0 likes -
Replying to @mausch
@mausch@davetchepak I can write a library that uses default once, then never use it again and be at least as productive.1 reply 0 retweets 0 likes -
Replying to @dibblego
@dibblego@davetchepak VBNET at least overloads the "Nothing" keyword to mean both null and default value type instance :-)1 reply 0 retweets 0 likes
@mausch @davetchepak You are not making my Friday very fun.
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.