[IronPython] Improving performance with stronger typing

[Harry Pierson]

VB.NET supports this kind of strong duck typing today. Furthermore, the next version of VB will support interface based duck typing, which combines strong typing benefits like intellisense with traditional duck typing benefits. Under the covers, the VB.NET compiler is generating reflection code to make the duck typed calls. Check out the "Dynamic Interfaces" section of  http://msdn.microsoft.com/library/en-us/dnvs05/html/vb9overview.asp <http://msdn.microsoft.com/vbasic/future/default.aspx?pull=/library/en-us/dnvs05/html/vb9overview.asp>  for more details.
 
Harry Pierson
Architect
Microsoft Architecture Strategy Team
email:                    hpierson at microsoft.com
IM/email:              harrypierson at hotmail.com
weblog:                 http://devhawk.net <http://.devhawk.net/>  
phone:                   425/705.6045
Make Trouble and Good Things Will Happen
 

________________________________

From: users-bounces at lists.ironpython.com on behalf of Andrew Deren
Sent: Tue 6/6/2006 9:04 AM
To: 'Discussion of IronPython'
Subject: Re: [IronPython] Improving performance with stronger typing



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.
Andrew

-----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
http://www.voidspace.org.uk/python/index.shtml

>-----
>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
>http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
>
> 
>

_______________________________________________
users mailing list
users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com


_______________________________________________
users mailing list
users at lists.ironpython.com
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com