🚀 go-pugleaf

In article  <8872@skye.cs.ed.ac.uk> Nick Rothwell writes:
]
]No runtime *type* errors. Runtime errors are restricted to a small set of
]exception conditions defined by the language.

The only runtime error you have eliminated with static type checking
is a "message not understood" or "domain error".  The elimination of
this single type of error hardly seems to justify the limitations on
expressiveness -- particularily since this is the easiest type of
error to find by testing.

The only reason you can kind find type errors at compile time is
because the errors are so trivial that the test is decidable.  How
much are you willing to give up in expressiveness to find the most
trivial and obvious programming error a few minutes earlier?
--
					David Gudeman
gudeman@cs.arizona.edu
noao!arizona!gudeman