So your static type checking project has the goal of producing C-performance code system. Meaning it can be compiled into machine code. Well the problem might be that code can make type assumptions and change types based on run-time events rather than build-time knowledge. So for example during run-time, some code would have to compile to execute the new run-time conditions. Interpreted code does this easily. How this relates to performance and static type checking? Perhaps my brain will figure this out, it kind of makes sense. Todd.
-- 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.
