[Types-sig] Static typing: Towards closure?

Skip Montanaro skip@mojam.com (Skip Montanaro)
Fri, 21 Jan 2000 12:05:10 -0600 (CST)

    Martijn> Note that runtime checking might help avoid the list of 1000
    Martijn> ints problem in some cases; this list can be declared to be of
    Martijn> ints and this can be checked at runtime, so that passing it
    Martijn> into checked function can proceed without overhead. But, if
    Martijn> this kind of thing is allowed, you could very well have a
    Martijn> type-infection problem; in order to avoid the overhead people
    Martijn> are pushed to add checks everywhere.

On which side of the function call is checking going to be performed?  If
it's in the called (and presumably typed) function, the person compiling the
calling code can't do anything to disable it short of recompiling the called
module with type checking disabled (which may not be an option).  And what
about extension modules?  Will -O execution disable them?

Skip Montanaro | http://www.mojam.com/
skip@mojam.com | http://www.musi-cal.com/