[IronPython] Improving performance with stronger typing

Andrew Deren andrew at adersoftware.com
Tue Jun 6 18:04:37 CEST 2006

I also have interest in this subject. I'm working on another language that
is as dynamic as python (even more so) and figuring out types is not easy.
You can do some advanced code analysis to find some cases where you can
guarantee the types, but that is not the most of the time.
PHP added type hints to class methods, so with those you can do it. Another
good example is boo language which looks similar to python but has strong
typing, but you can do "duck" typing too.

-----Original Message-----
From: users-bounces at lists.ironpython.com
[mailto:users-bounces at lists.ironpython.com] On Behalf Of Fuzzyman
Sent: Tuesday, June 06, 2006 4:02 AM
To: Discussion of IronPython
Subject: Re: [IronPython] Improving performance with stronger typing

Keith J. Farmer wrote:

>I can see it for primitive types, but not in general.
It sounds very interesting though. For circumstances where you are prepared
to guarantee the type of objects (and the range of operations permitted on
them), sacrificing dynamicity for speed sounds like a good trade off.

I've half had it in mind to write a compiler for a Python subset (as an
IronPython extension) that works similarly. Having no academic background in
the subject anything I did would be quite naive...

Michael Foord

>Keith J. Farmer // kfarmer at thuban.org
>-----Original Message-----
>From: users-bounces at lists.ironpython.com 
>[mailto:users-bounces at lists.ironpython.com] On Behalf Of Ben Blair
>add. Ideally, when the input types are known, IL should be emitted to just
do the add operation.
>users mailing list
>users at lists.ironpython.com

users mailing list
users at lists.ironpython.com

More information about the Ironpython-users mailing list