> Personally I find the convention of using `a', `b', and `c' for type > variables to be a poor one. I much prefer using `t' (if there's > only one) or `t1', `t2', ... (if there's more than one). > I find that for me this makes it much easier to read type declarations, > because names like `a', `b', and `c' sound like values, whereas names > like `t1', `t2', and `t3' suggest types. I *love* to use the same name for type variables and term variables, as in f :: a -> a f = \a -> a I also love to use the same name for type constructors and value constructors, as in data Foo a = Foo a Erik
- Haskell conventions (was: RE: how to write a simple ca... Jonathan King
- RE: Haskell conventions (was: RE: how to write a ... Frank A. Christoph
- Re: Haskell conventions (was: RE: how to write a ... Keith Wansbrough
- Re: Haskell conventions (was: RE: how to write a ... Jan Skibinski
- Re: Haskell conventions (was: RE: how to write a ... Jonathan King
- Re: Haskell conventions (was: RE: how to write a ... Craig Dickson
- Re: Haskell conventions (was: RE: how to write a ... Christian Sievers
- Re: Haskell conventions (was: RE: how to write a ... Jan Skibinski
- Re: Haskell conventions (was: RE: how to write a ... Craig Dickson
- Re: Haskell conventions (was: RE: how to write a ... Erik Meijer
- Re: Haskell conventions (was: RE: how to write a ... Fergus Henderson
- Re: Haskell conventions (was: RE: how to write a ... Friedrich Dominicus
- Re: Haskell conventions (was: RE: how to write a ... Jan de Wit