On Wed, Apr 6, 2011 at 6:58 PM, Edward K. Ream <[email protected]> wrote:
> 2. Super lint offers the possibility of speeding up important parts of > Leo by converting them to Pylint automatically. This is strictly an > experimental possibility, but I don't want to ignore it. I'm 95% sure this is not going to help. The parts that would most benefit from optimization (node iteration, @file parsing) are much easier to hand-optimize (with cython/c/c++) than by trying to create some automatic scheme. Any automatic scheme would just point out the things that are trivial anyway (e.g. "this is an int"). Better just to convert stuff to cython and start optimizing as appropriate. > 3. The main idea behind super lint, namely the strong intuition that > we programmers *do* know the types of almost all variables, has > intriguing possibilities for Leo's source code. It may, for example, > shed light on Leo's plugin mechanism. Type inference is a well investigated problem already, so it's useful to explore the prior art before using too much time on own research. The harder problem is how to make stuff fast once you know the types, not finding what the types are. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
