Changes between Version 25 and Version 26 of GhcApiStatus


Ignore:
Timestamp:
Aug 30, 2008 11:14:24 AM (7 years ago)
Author:
nominolo
Comment:

cleanups

Legend:

Unmodified
Added
Removed
Modified
  • GhcApiStatus

    v25 v26  
    247247   we need to keep it when a module is considered for compilation but not recompiled; when we generate the
    248248   `ModDetails` from the `ModIface`.  ToDo: find a better place to put it.
    249 
    250 == Change Log ==
    251 
    252  * introduced the {{{Ghc}}} monad which is (currently) defined as {{{Session -> IO (Either GhcError a)}}} where Session is mutabe.  This improves the following:
    253     * API functions no longer need to pass around sessions explicitly.  The single-threaded usage of a session is enforced.
    254     * More error information than a simple {{{Nothing}}}.
    255     * Errors can be handled in one place rather than case matching after each API call
    256     * ToDo: evaluate role of {{{log_action}}}
    257  * Functions that previously worked on a {{{Session}}} are now in {{{Ghc}}}.  {{{newSession}}} is now {{{withGhc}}} which is the exported run function for the {{{Ghc}}} monad.
    258  * {{{parseStaticFlags}}} has been removed, the functionality is now integrated with {{{withGhc}}}.  Before users had to be really careful in what order to call functions.
    259  * ATM, most things that import {{{GHC.hs}}} are broken due to the monadification.
    260249 
    261250== Open Issues ==
    262251
    263252 * Which operations should automatically call {{{clearWarnings}}}?
    264  * Get Haddock to work.
    265  * Error handling strategy.
    266253 * Remove {{{compileToCore}}} (it says it's there for backwards compatibility only)
    267254 * What's the deal with {{{SuccessFlag}}}?  Shouldn't that be {{{Either SomeError ()}}}?