Hi John,
I've extracted among others two things you don't like too much about
cabal:
a) having to specify build dependencies because they may change
(eg example split base or different libraries poviding network
interfaces ..)
b) Cabal can't do everything easily. Examples are the multi stage
This email is inspired by the discussion here: http://
hackage.haskell.org/trac/ghc/ticket/2401
As the ticket discusses, unsafeIOToSTM is, unlike unsafePerformIO or
unsafeInterleaveIO, genuinely completely unsafe in that there is no
way to use it such that a segfault or deadlock is not at
