On Fri, Sep 20, 2013 at 8:50 AM, Todd Mars <[email protected]> wrote:
> So your static type checking project has the goal of producing > C-performance code system. Meaning it can be compiled into machine code. > No. I didn't say that. I don't really know what the goals are. As an antidote for this somewhat ridiculous situation, I am focusing on the simplest useful tools that might detect *some* kinds of errors. > Well the problem might be that code can make type assumptions and change > types based on run-time events rather than build-time knowledge. > True, but we don't typically write programs that way. Indeed, *all* of Leo's functions and methods will quickly fail if they do not, in fact, receive arguments of the expected types. I assert (without proof ) that in this respect Python and C programs are similar. > So for example during run-time, some code would have to compile to execute > the new run-time conditions. Interpreted code does this easily. > The PyPy project uses a full-blown git, which does as you say. > How this relates to performance and static type checking? Perhaps my > brain will figure this out, it kind of makes sense. > :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
