GitLab

I tested FastTypes.lhs with hugs (manually using cpp) as well as ghc.

Closure uses now a list of Words instead of a ByteArray# to store the non ptrs.
Term.Prim follows this and keeps the [Word] value instead of storing the 
Show representation, which wasn't the best idea anyway.

This fixes test print022

This also means we don't need to carry around 10s of megs of Setup
executables in bindists.

Seemed like a reasonable thing to do, and only 1 line

Reset the exception flag before re-throwing the exception unless it
was "Interrupted".  This avoids needing the double :continue for
ordinary exceptions, but still lets us break on ^C.

when setting a breakpoint by coordinate, if there are no spans
covering the specified coordinate, then we take the leftmost of the
spans to the right of the coordinate.  This means that ':break c' will
work if c is not a function, because the first span will be on c's
right hand side.

Instead we identify the active expression with a line of ^^^^^^^
underneath it.

This gives us a chance to catch asynchronous exceptions (e.g. ^C) and break.

We never want to raise a StackOverflow exception inside
Control.Exception.block, because the user has no reasonable way of
handling it, and it invalidates some useful guarantees.

We don't support arbitrary unboxed tuples in GHCi right now.

See comments with shift_code

The docs were going in the wrong place before:
..../dist/docs instead of ..../docs

:cmd <expr> executes <expr> :: IO String, takes the resulting string
and executes it as a sequence of commands.  This is useful for doing
macro-ish things with ":set stop", for example.

I've taken material from Bernie's docs on the wiki, and Pepe's docs in
this file, and added some more material of my own.  Still to do:
document the individual commands.

This means that thunks under evaluation will have been updated with
the exception when we come to inspect them in GHCi.  Blackholes are
much less friendly.

When -fbreak-on-exception is set, an exception will cause GHCi to
suspend the current computation and return to the prompt, where the
history of the current evaluation can be inspected (if we are in
:trace).  This isn't on by default, because the behaviour could be
confusing: for example, ^C will cause a breakpoint.  It can be very
useful for finding the cause of a "head []" or a "fromJust Nothing",
though.

  ** This patch changes the interface file format.  All libraries etc **
  ** need to be compiled from scratch.                                **

- This adds the option to the flag reference and puts a stub pointing to the
  Haskell wiki page about type families into the section about type extensions.
- Once, the implementation has stabilised, the material from the wiki page 
  will be integreated into the user's manual.