1. 29 Aug, 2007 3 commits
  2. 28 Aug, 2007 4 commits
  3. 24 Aug, 2007 3 commits
  4. 28 Aug, 2007 3 commits
  5. 27 Aug, 2007 3 commits
    • mnislaih's avatar
      :stepover ---> :steplocal, :stepmodule · 3240dc3b
      mnislaih authored
       :stepover is declared a failed experiment. 
      :steplocal steps only on ticks contained in the current
      top level declaration. 
      :stepmodule steps only on ticks contained on the current
       module. 
      The current top level declaration and module are with
       respect to the breakpoint we are stopped on.
      
       The main reason for the failure of :stepover
      (apart from lacking a lexical call stack of course)
      is that it fails to detect when the expression being 
      evaluated is "complete", i.e. there are no ticks left in it.
      My assumption of the rightmost tick as the "last one",
      signaling that the expression is completely evaluated,
      is not true at all under laziness. 
      This assumption was key in the implementation of :stepover.
       
      3240dc3b
    • mnislaih's avatar
      Use a version of obtainTerm that takes a max depth bound · a27d12f0
      mnislaih authored
      when printing the contents of binding at a breakpoint
      a27d12f0
    • mnislaih's avatar
  6. 26 Aug, 2007 2 commits
  7. 24 Aug, 2007 1 commit
    • mnislaih's avatar
      A partial attempt to improve :stepover · 99794f66
      mnislaih authored
        
        With this patch, :stepover can effectively appear to step over recursive calls and 
        calls to locally bound functions (in a where clause).
        
        However, when we run out of ticks in the current expression, 
        the illusion vanishes and laziness brings us to the body of the last function 
        we "stepped over". 
        This is not desired at all, it is potentially very confusing.
        As a countermeasure, when this happens :stepover emits a warning
      
           "Warning: no more breakpoints in this function body, switching to :step"  
      99794f66
  8. 22 Aug, 2007 1 commit
  9. 28 Aug, 2007 1 commit
  10. 26 Aug, 2007 2 commits
    • Simon Marlow's avatar
      convert to use System.FilePath · fa6c4bf0
      Simon Marlow authored
      fa6c4bf0
    • Simon Marlow's avatar
      Refactoring only: remove [Id] field from ForeignStubs · 663b3914
      Simon Marlow authored
      We used to pass the list of top-level foreign exported bindings to the
      code generator so that it could create StablePtrs for them in the
      stginit code.  Now we don't use stginit unless profiling, and the
      StablePtrs are generated by C functions marked with
      attribute((constructor)).  This patch removes various bits associated
      with the old way of doing things, which were previously left in place
      in case we wanted to switch back, I presume.  Also I refactored
      dsForeigns to clean it up a bit.
      663b3914
  11. 28 Aug, 2007 1 commit
    • chak@cse.unsw.edu.au.'s avatar
      Type checking for type synonym families · 5822cb8d
      chak@cse.unsw.edu.au. authored
      This patch introduces type checking for type families of which associated
      type synonyms are a special case. E.g.
      
              type family Sum n m
      
              type instance Sum Zero n = n
              type instance Sum (Succ n) m = Succ (Sum n m)
      
      where
      
              data Zero       -- empty type
              data Succ n     -- empty type
      
      In addition we support equational constraints of the form:
      
              ty1 ~ ty2
      
      (where ty1 and ty2 are arbitrary tau types) in any context where
      type class constraints are already allowed, e.g.
      
              data Equals a b where
                      Equals :: a ~ b => Equals a b
      
      The above two syntactical extensions are disabled by default. Enable
      with the -XTypeFamilies flag.
      
      For further documentation about the patch, see:
      
              * the master plan
                http://hackage.haskell.org/trac/ghc/wiki/TypeFunctions
      
              * the user-level documentation
                http://haskell.org/haskellwiki/GHC/Indexed_types
      
      The patch is mostly backwards compatible, except for:
      
              * Some error messages have been changed slightly.
      
              * Type checking of GADTs now requires a bit more type declarations:
                not only should the type of a GADT case scrutinee be given, but also
                that of any identifiers used in the branches and the return type.
      
      Please report any unexpected behavior and incomprehensible error message 
      for existing code.
      
      Contributors (code and/or ideas):
              Tom Schrijvers
              Manuel Chakravarty
              Simon Peyton-Jones
              Martin Sulzmann 
      with special thanks to Roman Leshchinskiy
      5822cb8d
  12. 26 Aug, 2007 4 commits
  13. 25 Aug, 2007 8 commits
  14. 24 Aug, 2007 4 commits