1. 17 Dec, 2015 23 commits
  2. 16 Dec, 2015 13 commits
  3. 15 Dec, 2015 4 commits
    • Ben Gamari's avatar
      Expose enabled language extensions to TH · c1e25536
      Ben Gamari authored
      This exposes `template-haskell` functions for querying the language
      extensions which are enabled when compiling a module,
      - an `isExtEnabled` function to check whether an extension is enabled
      - an `extsEnabled` function to obtain a full list of enabled extensions
      To avoid code duplication this adds a `GHC.LanguageExtensions` module to
      `ghc-boot` and moves `DynFlags.ExtensionFlag` into it. A happy
      consequence of this is that the ungainly `DynFlags` lost around 500
      lines. Moreover, flags corresponding to language extensions are now
      clearly distinguished from other flags due to the `LangExt.*` prefix.
      Updates haddock submodule.
      This fixes #10820.
      Test Plan: validate
      Reviewers: austin, spinda, hvr, goldfire, alanz
      Reviewed By: goldfire
      Subscribers: mpickering, RyanGlScott, hvr, simonpj, thomie
      Differential Revision: https://phabricator.haskell.org/D1200
      GHC Trac Issues: #10820
    • Ben Gamari's avatar
      primops: Mark actions evaluated by `catch*` as lazy · 28638dfe
      Ben Gamari authored
      There is something very peculiar about the `catch` family of operations
      with respect to strictness analysis: they turn divergence into
      non-divergence. For this reason, it isn't safe to mark them as strict in
      the expression whose exceptions they are catching. The reason is this:
          let r = \st -> raiseIO# blah st
          in catch (\st -> ...(r st)..) handler st
      If we give the first argument of catch a strict signature, we'll get a
      demand 'C(S)' for 'r'; that is, 'r' is definitely called with one
      argument, which indeed it is. The trouble comes when we feed 'C(S)' into
      'r's RHS as the demand of the body as this will lead us to conclude that
      the whole 'let' will diverge; clearly this isn't right.
      This is essentially the problem in #10712, which arose when
      7c0fff41 marked the `catch*` primops as
      being strict in the thing to be evaluated. Here I've partially reverted
      this commit, again marking the first argument of these primops as lazy.
      Fixes #10712.
      Test Plan: Validate checking `exceptionsrun001`
      Reviewers: simonpj, austin
      Subscribers: thomie
      Differential Revision: https://phabricator.haskell.org/D1616
      GHC Trac Issues: #10712, #11222
    • Ben Gamari's avatar
      Add testcase for #11224 · a701694b
      Ben Gamari authored
      Test Plan: Validate
      Reviewers: austin, mpickering
      Reviewed By: mpickering
      Subscribers: mpickering, thomie
      Differential Revision: https://phabricator.haskell.org/D1622
      GHC Trac Issues: #11224
    • Ben Gamari's avatar
      base: NonEmpty: Fix documentation example · 758e6b3a
      Ben Gamari authored
      Fixes #11178.