Bug: this type supports the "null" value #2

Activity

1. pavel-khritonenko commented on Mar 7, 2015

   

   pavel-khritonenko

   on Mar 7, 2015

   More actions

   It should be struct instead of class
2. tpetricek commented on Mar 8, 2015

   

   tpetricek

   on Mar 8, 2015

   More actions

   Right! As things stand, having two possible values, the so-called type "nothing" is actually equivalent to "Boolean"!
3. Daniel15 commented on Mar 8, 2015

   

   Daniel15

   on Mar 8, 2015

   More actions

   public class AwesomeBoolean
   {
       public Nothing True { get { return Nothing.Instance; } }
       public Nothing False { get { return null; } }
   }
   
4. gregoryyoung commented on Mar 8, 2015

   

   gregoryyoung

   on Mar 8, 2015

   Owner

   More actions

   LOL!

   On Sun, Mar 8, 2015 at 8:57 AM, Daniel Lo Nigro notifications@github.com
   wrote:

   public class AwesomeBoolean
   {
   public Nothing True { get { return Nothing.Instance(); } }
   public Nothing False { get { return null; } }
   }

   —
   Reply to this email directly or view it on GitHub
   #2 (comment).

   Studying for the Turing test
5. dsyme commented on Mar 9, 2015

   

   dsyme

   on Mar 9, 2015

   Author

   More actions

   The proposed fix (also the one adding "sealed") means we can no longer inherit from Nothing.

   It seems clear that each and every thing "is a" nothing - maximum flexibility requires an open universe of possibilities (see also #24 (comment)).

   Further, inheriting a hidden something from Nothing is a well known tax avoidance strategy in some jurisdictions.
6. dsyme

   closed this as completedon Mar 9, 2015
7. dsyme

   reopened this on Mar 9, 2015