[Mention polymorphism. Fix a few ids. Bryan O'Sullivan **20070721165910] { hunk ./en/ch03-funcs-types.xml 137 - type Int, for example. + type Int, for example. We also call the list type + polymorphic, because it can contain any + type of value. hunk ./en/ch03-funcs-types.xml 145 - list. + list. We'll be spending a lot more time discussing lists in + . hunk ./en/ch03-funcs-types.xml 286 + Just as we called the list type polymorphic because it can + contain values of any type, when a function has type variables + in its signature, indicating that some of its arguments can be + of any type, we call the function polymorphic, too. + hunk ./en/ch03-funcs-types.xml 301 - parses these from right to left. If we introduce parentheses, - it makes it clearer how Haskell is interpreting this type - signature. + parses this chain of arrows from right to left. If we introduce + parentheses, it makes it clearer how Haskell is interpreting + this type signature. hunk ./en/ch03-funcs-types.xml 315 - soon, once we've spent a bit of time writing functions. + in , once we've spent a bit of + time writing functions. hunk ./en/ch04-fp.xml 8 - + hunk ./en/ch04-fp.xml 15 - + hunk ./en/ch04-fp.xml 22 - + hunk ./en/ch04-fp.xml 27 - - Partial Application + + Curried functions and partial application hunk ./en/ch04-fp.xml 32 - + hunk ./en/ch04-fp.xml 42 - + }