general parametrized types (was Re: Int overflow)

1997-10-29 Thread Stefan Karrmann
Hans Aberg wrote: > > Well, my idea is that all those types shouldsomehow be unified by a > single, parametrized type, which allows any bit length (not just 2^n), and > allowing signed/unsigned operations to be mixed without type conversion. > Together with the type-constructors used by monad

Re: Int overflow

1997-10-29 Thread Karl-Filip Faxen
There is a hidden cost to trapping Int overflow, beyond the extra instruction per operation mentioned by Paul Hudak. This is that operations on Ints become unsafe i.e. may raise exceptions (well that was the whole idea...). This is a problem both for a global instruction scheduler (e.g. a trace s

[kff@it.kth.se: Re: Int overflow]

1997-10-29 Thread Benjamin Goldberg
Karl-Filip Faxen <[EMAIL PROTECTED]> writes: > There is a hidden cost to trapping Int overflow ... > operations on Ints become unsafe i.e. may raise exceptions > This is a problem both for a global > instruction scheduler (e.g. a trace scheduler) and for other > optimizations based o

Re: Int overflow. Reply to reply to replies.

1997-10-29 Thread Hans Aberg
At 16:13 -0500 97/10/28, Alastair Reid wrote: >Once again, I refer people to the documentation for the shared Hugs-GHC >libraries. > > ftp://haskell.org/pub/reid/libs971028/libs.html > >As well as all the usual mutable stuff, these libraries provide the following > types: > > Int8, Int16, Int32,