unboxed types
Isaac Dupree
isaacdupree at charter.net
Mon Dec 31 09:14:04 EST 2007
I guess boxed types are too risky for efficiency reasons in some parts
of the code (close examination of -ddump-simpl would be needed I guess),
so I'll expand utils/FastTypes and put all the #ifdefs in there.
Unboxed tuples that are used in little areas of GHC code solely for the
efficiency of not containing _|_ nor polymorphism are a nuisance
syntactically. Can I
#ifdef __GLASGOW_HASKELL__
#define UT #
#else
#defined UT
#endif
and use (UT x, y UT)
?
Or will I have to
#define UTopen (#
#defined UTclose #)
and (UTopen x, y UTclose)
... does that seem fairly reasonable?
Isaac
More information about the Cvs-ghc
mailing list