Oops posted too soon :) On Wednesday, January 7, 2015 10:37:01 AM UTC+10, [email protected] wrote: > > [...] >> >> This definition will be type-stable (it will always return a >> Nullable{Bool}) and it will be able to signal all three possible results; >> get(a) == b, get(a) != b and get(a) == null. >> > Forgot to say Base.== returns bool, so this now makes == type unstable.
> > It is then messy to use == in an if when the return is not a bool. > > In fact you still have to write the isnull() test which is essentially the > same code as your definition of == so nothing has been gained by defining > ==. > > Cheers > Lex > > > >> >> [...] >> >
