Closed daviis closed 9 years ago
Nope, we don't. This came about because of the 'x is y' statement. But is and is not will never throw a type error because everything extends from a base object so there is no real need to check it. Currently is an isnot are just special cased.
Need to build up a FunDefBean in visit_compare then call self.namespace.checkCall(class, fundefBean) or something like that...