I actually hit <tab><enter> as part of coding and didn't mean to submit that yet. The __init__() function was supposed to also store the args and kw arguments.

class ImmutablePoint
{
int m_x;
int m_y;
int x { get { return m_x; } }
int y { get { return m_y; } }
ImmutablePoint(int x, int y)
{
m_x = x;
m_y = y;
}
}

Incidentally, I think part of the problem with types (and the reason many people feel ambivalent about them) is that many languages force you to do a lot of extra typing (no pun intended) in order to tell the compiler about each data structure. What you really want to say is “Listen, compiler, an ImmutablePoint is a pair of ints, called ‘x’ and ‘y’, and it never changes once constructed.” And get on with your programming.

I think I’ll ivent a programming language with the “#listen_compiler” directive.

<pre>
class lazy:
def __init__(self, function, *args, **kw):
self.function = function

def __getattr__(self, k):
# evaluate function(*args, **kw) and remember the return value (self.rv)
# return self.rv.__getattr__(k)
</pre>

I actually hit <tab><enter> as part of coding and didn’t mean to submit that yet. The __init__() function was supposed to also store the args and kw arguments.

Too much work to do it just once. See my comments idea for more info on how it should really be done.