🚀 go-pugleaf

Jim Giles:
   Yes, this is what I want.  Can you give an example of how to do it
   that's actually statically checked?

Not until I (or someone else) gets a compiler working.  Presently I'm
talking pretty much in theoretical terms.

   How do you guard against reassignments?  Note, the `colon'
   definitions you described earlier prevent the identifier from being
   reassigned at all.  What I want is to allow the _value_ to be
   assigned without allowing the type to ever be alterred.

I need to think about this one a bit more.  For example, how would you
deal with the case where the type of an object is "an active element
of database blahblah"?

From my experience, the significant problem area in large programs is
race conditions.  If there's no race condition, there's no need to do
the reassignment in the first place.

And, I don't know about you, but to me it seems kind of silly to
introduce a "safety mechanism" that entirely ignores the big picture.

-- 
Raul Deluth Miller-Rockwell                   <rockwell@socrates.umd.edu>