1. 09 Jun, 2007 1 commit
  2. 08 Jun, 2007 3 commits
    • andy@galois.com's avatar
      7a77f1b7
    • chak@cse.unsw.edu.au.'s avatar
      Fix worker/wrapper ids for newtype instances · ef0ef4cc
      chak@cse.unsw.edu.au. authored
      - mkDataConIds forced an algebraic worker/wrapper on newtype instances (not
        on vanilla newtypes).  I am not sure where this came from (from code I
        wrote or from the recent restructuring of MkIds), but its not the right
        thing to do.  In particular, it requires newtype instances to have con_info
        labels in the generated code, which makes no sense.
      - Worker construction for newtypes is smart enough that it will construct the
        right signature for newtype instances (ie, one that mentions the family
        type constructor, not the instance tycon).
      ef0ef4cc
    • chak@cse.unsw.edu.au.'s avatar
      Fix deriving of indexed data types · 39dca315
      chak@cse.unsw.edu.au. authored
      - Fix typo introduced when moving deriving-specific code from TcEnv to TcDeriv
      - Thanks to Roman for the bug report
      39dca315
  3. 07 Jun, 2007 1 commit
  4. 06 Jun, 2007 3 commits
    • simonpj@microsoft.com's avatar
      Don't suggest -fno-monomorphism-restriction if it's already set · ffe3d0b6
      simonpj@microsoft.com authored
      This patch implements the suggestion in Trac #1398.  It's obviously
      stupid to suggest -fno-monomorphism-restriction if the user is already
      using it.  
      
      (Maybe another suggestion would be good, but this one clearly bogus.)
      ffe3d0b6
    • simonpj@microsoft.com's avatar
      Remove unnecessary free-variables from renamer · 3c4a732b
      simonpj@microsoft.com authored
      The renamer used to be responsible for making sure that all interfaces
      with instance decls (other than orphans) were loaded.  But TH makes that
      impossible, so the typechecker does it, via checkWiredInTyCon.
      
      This patch simply removes redundant additions to the free-variable set
      in the renamer, which were there, I believe, solely to ensure that the 
      instances came in.  Removing them should change nothing, but it's a 
      useful clean up.
      3c4a732b
    • simonpj@microsoft.com's avatar
      FIX #1385: make sure tuple instances are loaded · f750bec7
      simonpj@microsoft.com authored
      Typechecking of explicit tuples is done "by hand" (rather than using
      boxySplitTyConApp) so that rigidity is maintained.  In making that change
      I'd forgotten to retain the call to checkWiredInTyCon, which is important
      to make sure instances are brought into scope.
      
      Test is tc227.
      
      f750bec7
  5. 05 Jun, 2007 7 commits
  6. 01 Jun, 2007 2 commits
  7. 21 May, 2007 1 commit
  8. 25 May, 2007 1 commit
  9. 01 Jun, 2007 1 commit
  10. 31 May, 2007 3 commits
  11. 30 May, 2007 5 commits
  12. 25 May, 2007 2 commits
  13. 29 May, 2007 1 commit
  14. 26 May, 2007 3 commits
  15. 29 May, 2007 2 commits
  16. 26 May, 2007 1 commit
  17. 25 May, 2007 3 commits