RE: Primitive types and Prelude shenanigans

| Why not just let | | if x then y else z | | be syntactic sugar for | | Prelude.ifThenElse x y z The burden of my original message was that a) this is reasonable, but b) it would have to become the *defined behaviour* As you say, the "defined behaviour" would have to cover guards as well, and I'm not absolutely certain what else. The way GHC is set up now, it's relatively easy to make such changes (this wasn't true before). But it takes some design work. If someone cares enough to do the design work, and actively wants the result, I'll see how hard it is to implement. Simon

Wed, 28 Feb 2001 02:05:27 -0800, Simon Peyton-Jones
If someone cares enough to do the design work, and actively wants the result, I'll see how hard it is to implement.
IMHO it should not be done only because it's possible. If a part of Prelude is to be replaceable, there should be a chance that it's useful for something. You can't replace the whole Prelude anyway, e.g. (->) and Integer don't look as if it was possible for them. -- __("< Marcin Kowalczyk * qrczak@knm.org.pl http://qrczak.ids.net.pl/ \__/ ^^ SYGNATURA ZASTÊPCZA QRCZAK

On Wed, Feb 28, 2001 at 02:05:27AM -0800, Simon Peyton-Jones wrote:
If someone cares enough to do the design work, and actively wants the result, I'll see how hard it is to implement.
I've been thinking some about the design, and I'd be happy to finish it, but I can't honestly say I would use it much (other than for the numeric types) in the near future. Best, Dylan Thurston
participants (3)
-
Dylan Thurston
-
qrczak@knm.org.pl
-
Simon Peyton-Jones