IntInf asserts (fwd)

[Stephen Weeks]

> Well, we could always change the types of things like:
> 
> 	    val + = _prim "IntInf_add": int * int * word array -> int;
> 
> to
> 
> 	    val + = _prim "IntInf_add": int * int * Int.int -> int;
> 
> It should be easy to increment the frontier by that third argument; now,
> it depends on how much the intInf code depends on that array be
> initialized in the appropriate way, or if it will just trash whatever is
> there.
> 
> What this really adds is to the limitCheck insertion code, which now needs
> to know that IntInf_add and friends do implicit allocation, just like
> Array_array does.  

I don't object to this, and it does solve the flatten problem.