| The user's guide is silent about which version of Eq is used | for literal patterns, but I assume that it follows the (n+k) | example and so Prelude Eq is used for the overloaded use of ==. That's right. I'll add a note to that effect in the users guide. | What is the reason for using Prelude.Ord (and Prelude.Eq)? | | This seems very limiting since you can replace Num but you | can't replace Eq, and moreover, your new versions of the | Numeric classes must be subclasses of Prelude.Eq, rather than | another Eq. |... | Is there are strong reason for avoiding the alternative: | "whatever == and >= are in scope"? Perhaps it is the | if-then-else that must refer to Prelude.Bool? Well, I had to stop somewhere. (As I have previously remarked on this thread, it is hard to make *everything* rebindable.) With more effort one could make more things rebindable. My goal was to make numerics completely rebindable; the current omission is (only) the handling of defaults. At the moment I simpy don't know what a good 'final' design might be, and I'm pretty reluctant to develop this feature incrementally. If a consensus emerges, then yes (unless it's a heart-and-lung job) I'll implement it or help one of you to do so. Simon