Am Donnerstag, 23. Februar 2006 02:47 schrieb John Meacham: > [...] > But more importantly, The haskell module system has a nice philosophy of > just being about controlling the namespace of what is in scope in a > module. Conflating representation details with it would just confuse > things. I'd say use 'type' for everything in the type namespace, class > for everything in the class namespace, value (or nothing) for things in > the value namespace and so forth. We want the module system to describe > precicely what names are in scope and what entities names in a module > map too, nothing more. It is also a much simpler set of rules to > remember and much more straightforward to specify.
The remaining problem is that using "type" for every type is misleading, since "type" is otherwise used only for aliases. Maybe it would be better to use something like "typealias" for type aliases, since using "type" for declaring type aliases is misleading anyway. > John Best wishes, Wolfgang _______________________________________________ Haskell-prime mailing list Haskell-prime@haskell.org http://haskell.org/mailman/listinfo/haskell-prime
