Lisandro Dalcin wrote: > Perhaps it is time to generate Cython compile-time warning when > calling with an untyped arg value? Again, an explicit cast would > suppress the warning... > [...] > BTW, perhaps all this stuff is important enough as to start a new thread?
Yep, I guess so. > In the future, you could optimize item access for "bytes" ? That's worth a feature request in trac, I'd say. Although you'd normally cast a byte string to a char* anyway if you want to do performance critical operations on it... > Additionally, you could need to use typed variables because you want > to enforce automatic compile-time/runtime type-checking on assignement > or when calling functions ... Or you want to save the type-check > before call, as in foo(c) in my example above When are we finally getting the tiny bit of type inference that's necessary to do this internally? Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
