Pozorvlak

http://wiesmann.codiferes.net/wordpress/?p=15187&lang=en

Falsehoods programmers believe about geography

http://www.mjt.me.uk/posts/falsehoods-programmers-believe-about-addresses/

Falsehoods programmers believe about addresses

http://www.cscyphers.com/blog/2012/06/28/falsehoods-programmers-believe-about-gender/

Falsehoods programmers believe about gender

http://erratasec.blogspot.com/2012/06/falsehoods-programmers-believe-about.html#.UaeWSGSG1qI

Falsehoods programmers believe about networks

http://pozorvlak.livejournal.com/174763.html

Falsehoods programmers believe about build systems

http://infiniteundo.com/post/25326999628/falsehoods-programmers-believe-about-time

Falsehoods programmers believe about time

http://butgrace.com/2012/06/19/more-falsehoods-programmers-believe-about-time/

More falsehoods programmers believe about time

Your class will not work without language-level if/else construct or something equivalent. In Samlltalk if/else is implemented purely through message passing. There is no "real" if/else.

IIRC, Smalltalk has Boolean class and two subclasses of Boolean: True and False. There is a single method with two arguments (:ifTrue:ifFlase). The method is then overloaded. True calls ifTrue argument. Flase calls ifFalse argument. This is happening dynamically, at runtime. Again, the mechanism is generic enough to fully replace all use cases of "traditional" if/else constructs.

Clearly, you haven't thought this through.

Edit:
People here would do well to read this:
https://pozorvlak.livejournal.com/94558.html