Robert Bradshaw wrote: >> I could just >>stop taking any notice of 'or None' and 'not None' >>declarations. They would be allowed so that old code >>would still compile, but they would be ignored. > > But people would start depending on this, and then ignoring those > checks would break people's code in other ways.
In what ways are you imagining that people would depend on it? The only way I can see of it breaking code is if someone relied on a TypeError getting raised at the exact point where a function was entered, instead of waiting until a bit later. That seems like a rather unlikely scenario to me. -- Greg _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
