1. 25 Jul, 2015 1 commit
    • Sergei Trofimovich's avatar
      renamer: fix module-level deprecation message · b04bed0a
      Sergei Trofimovich authored
      Noticed today that deprecation warnings are
      slightly broken in -HEAD:
      
        mtl-2.2.1/Control/Monad/Error/Class.hs:46:1: warning:
          Module ‘Control.Monad.Trans.Error’ is deprecated:
            ([", U, s, e,  , C, o, n, t, r, o, l, ., M, o, n, a, d, ., T, r, a,
              n, s, ., E, x, c, e, p, t,  , i, n, s, t, e, a, d, "],
             Use Control.Monad.Trans.Except instead)
      
      Commit e6191d1c
      slightly changed WarningTxt declaration:
      
      -data WarningTxt = WarningTxt (Located SourceText) [Located FastString]
      -                | DeprecatedTxt (Located SourceText) [Located FastString]
      +data WarningTxt = WarningTxt (Located SourceText)
      +                             [Located (SourceText,FastString)]
      +                | DeprecatedTxt (Located SourceText)
      +                                [Located (SourceText,FastString)]
      
      But 'moduleWarn' function was not updated to do the stripping.
      Signed-off-by: default avatarSergei Trofimovich <siarheit@google.com>
      
      Reviewers: austin, bgamari, hvr, goldfire, rwbarton, alanz
      
      Reviewed By: rwbarton, alanz
      
      Subscribers: thomie
      
      Differential Revision: https://phabricator.haskell.org/D1096
      
      GHC Trac Issues: #10313
      b04bed0a
  2. 24 Jul, 2015 6 commits
    • Ben Gamari's avatar
      09d05050
    • Simon Peyton Jones's avatar
      Improve instanceCantMatch · 6e618d77
      Simon Peyton Jones authored
      When staring at instanceCantMatch I realised that it
      was returning False (safe but inefficient) when it could
      validly return True, on arguments like
         [Nothing,   Just Int]
         [Just Bool, Just Bool]
      
      This patch makes it a bit cleverer.
      6e618d77
    • Simon Peyton Jones's avatar
      Refactoring around FunDeps · d53d8089
      Simon Peyton Jones authored
      This refactoring was triggered by Trac #10675.
      
      We were using 'improveClsFD' (previously called 'checkClsFD') for
      both
        * Improvement: improving a constraint against top-level instances
        * Consistency: checking when two top-level instances are
          consistent
      
      Using the same code for both seemed attractive at the time, but
      it's just too complicated.  So I've split it:
       * Improvement: improveClsFD
       * Consistency: checkFunDeps
      
      Much clearer now!
      d53d8089
    • Simon Peyton Jones's avatar
      Comments about stricteness of catch# · e1616343
      Simon Peyton Jones authored
      In "Improve strictness analysis for exceptions"
         commit 7c0fff41
         Author: Simon Peyton Jones <simonpj@microsoft.com>
         Date:   Tue Jul 21 12:28:42 2015 +0100
      
      I made catch# strict in its first argument.  But today I found
      a very old comment suggesting the opposite.  I disagree with the
      old comment, but I've elaborated the Note, which I reproduce here:
      
          {- Note [Strictness for mask/unmask/catch]
          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
          Consider this example, which comes from GHC.IO.Handle.Internals:
             wantReadableHandle3 f ma b st
               = case ... of
                   DEFAULT -> case ma of MVar a -> ...
                   0#      -> maskAsynchExceptions#
                                 (\st -> case ma of MVar a -> ...)
          The outer case just decides whether to mask exceptions, but we
          don't want thereby to hide the strictness in 'ma'!  Hence the use
          of strictApply1Dmd.
      
          For catch, we know that the first branch will be evaluated, but
          not necessarily the second.  Hence strictApply1Dmd and
          lazyApply1Dmd
      
          Howver, consider
              catch# (\st -> case x of ...) (..handler..) st
          We'll see that the entire thing is strict in 'x', so 'x' may be
          evaluated before the catch#.  So fi evaluting 'x' causes a
          divide-by-zero exception, it won't be caught.  This seems
          acceptable:
            - x might be evaluated somewhere else outside the catch# anyway
            - It's an imprecise eception anyway.  Synchronous exceptions (in
              the IO monad) will never move in this way.
          There was originally a comment
            "Catch is actually strict in its first argument
             but we don't want to tell the strictness
             analyser about that, so that exceptions stay inside it."
          but tracing it back through the commit logs did not give any
          rationale.  And making catch# lazy has performance costs for
          everyone.
      e1616343
    • Simon Peyton Jones's avatar
      Comments only · 30d8349a
      Simon Peyton Jones authored
      30d8349a
    • Ben Gamari's avatar
      Fix line number in T10018 testcase · 45c319ff
      Ben Gamari authored
      45c319ff
  3. 23 Jul, 2015 14 commits
    • Edward Z. Yang's avatar
      Library names, with Cabal submodule update · f9687caf
      Edward Z. Yang authored
      A library name is a package name, package version, and hash of the
      version names of all textual dependencies (i.e. packages which were included.) A library
      name is a coarse approximation of installed package IDs, which are suitable for
      inclusion in package keys (you don't want to put an IPID in a package key, since
      it means the key will change any time the source changes.)
      
          - We define ShPackageKey, which is the semantic object which
            is hashed into a PackageKey.  You can use 'newPackageKey'
            to hash a ShPackageKey to a PackageKey
      
          - Given a PackageKey, we can lookup its ShPackageKey with
            'lookupPackageKey'.  The way we can do this is by consulting
            the 'pkgKeyCache', which records a reverse mapping from
            every hash to the ShPackageKey.  This means that if you
            load in PackageKeys from external sources (e.g. interface
            files), you also need to load in a mapping of PackageKeys
            to their ShPackageKeys so we can populate the cache.
      
          - We define a 'LibraryName' which encapsulates the full
            depenency resolution that Cabal may have selected; this
            is opaque to GHC but can be used to distinguish different
            versions of a package.
      
          - Definite packages don't have an interesting PackageKey,
            so we rely on Cabal to pass them to us.
      
          - We can pretty-print package keys while displaying the
            instantiation, but it's not wired up to anything (e.g.
            the Outputable instance of PackageKey).
      Signed-off-by: default avatarEdward Z. Yang <ezyang@cs.stanford.edu>
      
      Test Plan: validate
      
      Reviewers: austin, bgamari
      
      Subscribers: thomie
      
      Differential Revision: https://phabricator.haskell.org/D1056
      
      GHC Trac Issues: #10566
      f9687caf
    • Ben Gamari's avatar
      5ff4dadd
    • thomie's avatar
      ghci: fixity declarations for infix data constructors (#10018) · e809ef57
      thomie authored
      Declaring a custom fixity for an infix data constructor should work:
      
          Prelude> data Infix a b = a :@: b; infixl 4 :@:
      
      This is a followup to #2947, which handled fixity declarations in ghci
      statements (e.g. let add = (+); infixl 6 `add`).
      
      Support for declarations (data, type, newtype, class, instance,
      deriving, and foreign) was added to GHCi in #4929.
      
      Reviewers: simonpj, austin, thomie
      
      Subscribers: thomie, bgamari
      
      Differential Revision: https://phabricator.haskell.org/D1028
      
      GHC Trac Issues: #10018
      e809ef57
    • Simon Peyton Jones's avatar
      608e76ce
    • Simon Peyton Jones's avatar
      Slight refactoring to the fix for #4012 · 7ec07e40
      Simon Peyton Jones authored
      Add CoreSyn.chooseOrphanAnchor, and use it
      7ec07e40
    • Ben Gamari's avatar
      rts/sm: Add missing argument names in function definitions · 4c8e69e0
      Ben Gamari authored
      C99 does not allow unnamed parameters in definition argument lists [1].
      
      [1] http://stackoverflow.com/questions/8776810/parameter-name-omitted-c-vs-c
      4c8e69e0
    • Ben Gamari's avatar
      DataCon: Fix redundant import · 1852c3d2
      Ben Gamari authored
      1852c3d2
    • thomasw's avatar
      Parenthesise TypeOperator in import hints · b5c94262
      thomasw authored
      When a constructor was mistakenly imported directly instead of as a
      constructor of a data type, a hint will be shown on how to correctly
      import
      it. Just like the constructor, the data type should be surrounded in
      parentheses if it is an operator (TypeOperator in this case).
      
      Instead of:
      
          error:
              In module ‘Data.Type.Equality’:
                ‘Refl’ is a data constructor of ‘:~:’
              To import it use
                ‘import’ Data.Type.Equality( :~:( Refl ) )
              or
                ‘import’ Data.Type.Equality( :~:(..) )
      
      Print:
      
          error:
              In module ‘Data.Type.Equality’:
                ‘Refl’ is a data constructor of ‘(:~:)’
              To import it use
                ‘import’ Data.Type.Equality( (:~:)( Refl ) )
              or
                ‘import’ Data.Type.Equality( (:~:)(..) )
      
      Test Plan: pass new test
      
      Reviewers: austin, bgamari, simonpj
      
      Reviewed By: simonpj
      
      Subscribers: simonpj, thomie
      
      Differential Revision: https://phabricator.haskell.org/D1093
      
      GHC Trac Issues: #10668
      b5c94262
    • rwbarton's avatar
      Update encoding001 to test the full range of non-surrogate code points · e78841b5
      rwbarton authored
      GHC has used surrogate code points for roundtripping since 7.4.
      See Note [Roundtripping].
      
      Also, improve the wording of that Note slightly.
      
      Test Plan: validate still passes
      
      Reviewers: austin, hvr, bgamari
      
      Reviewed By: bgamari
      
      Subscribers: thomie
      
      Differential Revision: https://phabricator.haskell.org/D1087
      e78841b5
    • Ben Gamari's avatar
      Accept next-docstrings on GADT constructors. · 76e2341a
      Ben Gamari authored
      Accept next docstrings (`-- | Docstring`) on GADT constructors.
      
      I have confirmed that this adds no shift/reduce conflicts.
      
      Test Plan: haddockA034
      
      Reviewers: austin, simonpj, simonmar
      
      Reviewed By: simonmar
      
      Subscribers: Fuuzetsu, simonmar, thomie, mpickering, edsko
      
      Differential Revision: https://phabricator.haskell.org/D1086
      76e2341a
    • spinda's avatar
      Generate .dyn_o files for .hsig files with -dynamic-too · d2b4df15
      spinda authored
      With -dynamic-too, .dyn_o files were not being generated for .hsig
      files.  Normally, this is handled in the pipeline; however, the branch
      for .hsig files called compileEmptyStub directly instead of going
      through runPipeline.  When compiling a Cabal package that included .hsig
      files, this triggered a linker error later on, as it expected a .dyn_o
      file to have been generated for each .hsig.
      
      The fix is to use runPipeline for .hsig files, just as with .hs files.
      Alternately, one could duplicate the logic for handling -dynamic-too in
      the .hsig branch, but simply calling runPipeline ends up being much
      cleaner.
      
      Test Plan: validate
      
      Reviewers: austin, ezyang, bgamari, thomie
      
      Reviewed By: ezyang, thomie
      
      Subscribers: thomie
      
      Differential Revision: https://phabricator.haskell.org/D1084
      
      GHC Trac Issues: #10660
      d2b4df15
    • thomie's avatar
      Lexer: support consecutive references to Haddock chunks (#10398) · d784bdeb
      thomie authored
      Reviewers: austin, bgamari, Fuuzetsu
      
      Reviewed By: bgamari
      
      Subscribers: thomie, bgamari
      
      Differential Revision: https://phabricator.haskell.org/D1025
      
      GHC Trac Issues: #10398
      d784bdeb
    • Simon Peyton Jones's avatar
      Comments only · 98512751
      Simon Peyton Jones authored
      98512751
    • Simon Peyton Jones's avatar
      Fix Trac #10670 · 5c3fc921
      Simon Peyton Jones authored
      In dataConCannotMatch we were using a GADT data con without
      properly instantiating the existential type variables.
      The fix is easy, and the code is tighter.
      5c3fc921
  4. 22 Jul, 2015 12 commits
  5. 21 Jul, 2015 7 commits