Re: [Haskell-cafe] Non-atomic "atoms" for type-level programming

15 Apr 2009

      Am Dienstag, 14. April 2009 20:01 schrieb Tillmann Rendel:
...
How is the need for a common import for 'data TTrue; data TFalse'
different then the need for a common import for 'data Bool = True | False'?
Why not say

    data True

    data False,

instead of

    data TTrue

    data TFalse?

I don’t see the reason why we should insert the “T”. Data constructors are in 
a different namespace than type constructors.

By the way, the grapefruit-records package imports type-level, only to not 
define its own type-level booleans but to reuse “common” types whereas I 
considered type-level as the standard type level programming library.

Best wishes,
Wolfgang

Re: [Haskell-cafe] Non-atomic "atoms" for type-level programming

Wolfgang Jeltsch