1. 02 May, 2007 4 commits
  2. 27 Apr, 2007 1 commit
  3. 25 Apr, 2007 3 commits
  4. 02 May, 2007 2 commits
  5. 01 May, 2007 4 commits
  6. 30 Apr, 2007 10 commits
  7. 29 Apr, 2007 3 commits
  8. 27 Apr, 2007 9 commits
  9. 26 Apr, 2007 4 commits
    • Simon Marlow's avatar
      restore the correct Unicode ellipsis character · b360a336
      Simon Marlow authored
      It looks like this was accidentally replaced with '?' in the patch
      "HsSyn clean up for indexed types".  (see bug #1294)
    • chevalier@alum.wellesley.edu's avatar
      Avoid segfault when ticky file argument is stderr · ed95d86d
      chevalier@alum.wellesley.edu authored
      If you compiled a program with -ticky and ran it with:
      ./foo +RTS -rstderr -RTS
      the result would be a segfault. This was because the RTS interprets stderr to
      mean "use debugBelch to print out messages," and sets the ticky file pointer
      to NULL as a result, but PrintTickyInfo (the function in Ticky.c that prints
      out the ticky report) wasn't checking for NULL.
      I changed PrintTickyInfo to check whether the ticky file pointer is NULL and 
      output to stderr if so.
      Also removed an unused import from CodeOutput.lhs.
    • mnislaih's avatar
      Dont tidy up tyvars after :print type reconstruction · cdfe9b08
      mnislaih authored
      I introduced a bug yesterday when I changed the way tidying up was performed.
      As a result of tidying,  cvObtainTerm could be returning types 
      with regular tyvars inside, which never should.
      But actually, it's better if we do not do the tidying up, in order to 
      keep the tyvar names from the environment.
      New names will be introduced only when an existential is found, which
      is not so common. In this case the user will see a funny name. 
      Is that really an issue?
    • Simon Marlow's avatar