RE: how to break up a large module?
A non-exported function can be inlined, and its definition deleted. If there is only one call site, it can be inlined no matter how big it is. S | -----Original Message----- | From: haskell-cafe-admin@haskell.org [mailto:haskell-cafe-admin@haskell.org] On Behalf Of Jerzy | Karczmarczuk | Sent: 30 May 2003 14:04 | To: haskell-cafe@haskell.org | Subject: Re: how to break up a large module? | | Simon Marlow wrote: | | > Be careful about accidental overloading: | ... | | > Be careful with exports. Prune export lists to just those functions | > which need to be exported. | | | How a too long export list can slow-down the target program? | | Jerzy Karczmarczuk | | _______________________________________________ | Haskell-Cafe mailing list | Haskell-Cafe@haskell.org | http://www.haskell.org/mailman/listinfo/haskell-cafe
Hi, I think that there is consensus regarding the usefulness of overlapping instances. But it is a pitty that the -fallow-overlapping-instances declaration is so pervasive. I mean: - If I deal with several classes, only few of them require overlapping instances, then I would like to restrict -fallow to the relevant classes. - If I compile a module A with overlapping instances allowed, and I import A into B, then I don't want to be forced to allow overlapping instances in B unless B by itself wants to produce overlaps. Did I miss anything? If not, would that be difficult (formally, technically)? Ralf -- Ralf Laemmel VU & CWI, Amsterdam, The Netherlands http://www.cs.vu.nl/~ralf/ http://www.cwi.nl/~ralf/
participants (2)
-
Ralf Laemmel -
Simon Peyton-Jones