Dag Sverre Seljebotn wrote: > a) first implement things in Python (or at least in untyped Cython) > b) profile (or at least experience that things are too slow) > c) find out which functions you bother to type, and incrementally type > your program "bottom up". > > Now, if we suddenly change the meaning of operators depending on whether > they operate on Python ints or C ints, it means that an algorithm that > worked perfectly in step a) will break in step c). Which just means more > hassle, and that step c) become a bigger job than it needs to be.
That's also where I see the difference to things like overflows: you have to think about them anyway when you restrict the value range through typing (e.g. a Python long into a C long). But having an operator change its result just because you just typed one of its input variables seems like a rather dangerous trap that's hard to track down. Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
