On Thu, Feb 23, 2006 at 11:36:34AM +0100, Wolfgang Jeltsch wrote:
> 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.
I don't think it is that misleading, when you have
data Foo = Bar | Baz
I think of the name 'Foo' as a type. You say x has type Foo. not x has
data Foo.
type synonyms do nothing but introduce a new type name which is why it
is declared with 'type', but data and newtype introduce a typename and
something else. but refering to just the name as a 'type' is consistent
with usage.
not that the terminology is perfect, but I don't think it is odd enough
to warrent changing or worrying too much about.
John
--
John Meacham - ⑆repetae.net⑆john⑈
_______________________________________________
Haskell-prime mailing list
Haskell-prime@haskell.org
http://haskell.org/mailman/listinfo/haskell-prime
