1. 27 Sep, 2020 1 commit
  2. 26 Sep, 2020 20 commits
  3. 24 Sep, 2020 9 commits
    • Hécate Moonlight's avatar
    • Sebastian Graf's avatar
    • Simon Peyton Jones's avatar
      Improve kind generalisation, error messages · 9fa26aa1
      Simon Peyton Jones authored
      This patch does two things:
      * It refactors GHC.Tc.Errors a bit.  In debugging Quick Look I was
        forced to look in detail at error messages, and ended up doing a bit
        of refactoring, esp in mkTyVarEqErr'.  It's still quite a mess, but
        a bit better, I think.
      * It makes a significant improvement to the kind checking of type and
        class declarations. Specifically, we now ensure that if kind
        checking fails with an unsolved constraint, all the skolems are in
        scope.  That wasn't the case before, which led to some obscure error
        messages; and occasional failures with "no skolem info" (eg #16245).
      Both of these, and the main Quick Look patch itself, affect a /lot/ of
      error messages, as you can see from the number of files changed.  I've
      checked them all; I think they are as good or better than before.
      Smaller things
      * I documented the various instances of VarBndr better.
        See Note [The VarBndr tyep and its uses] in GHC.Types.Var
      * Renamed GHC.Tc.Solver.simpl_top to simplifyTopWanteds
      * A bit of refactoring in bindExplicitTKTele, to avoid the
        footwork with Either.  Simpler now.
      * Move promoteTyVar from GHC.Tc.Solver to GHC.Tc.Utils.TcMType
      Fixes #16245 (comment 211369), memorialised as
      Also fixes the three bugs in #18640
    • Simon Peyton Jones's avatar
      Implement Quick Look impredicativity · 97cff919
      Simon Peyton Jones authored
      This patch implements Quick Look impredicativity (#18126), sticking
      very closely to the design in
          A quick look at impredicativity, Serrano et al, ICFP 2020
      The main change is that a big chunk of GHC.Tc.Gen.Expr has been
      extracted to two new modules
      which deal with typechecking n-ary applications, and the head of
      such applications, respectively.  Both contain a good deal of
      Three other loosely-related changes are in this patch:
      * I implemented (partly by accident) points (2,3)) of the accepted GHC
        proposal "Clean up printing of foralls", namely
        (see #16320).
        In particular, see Note [TcRnExprMode] in GHC.Tc.Module
        - :type instantiates /inferred/, but not /specified/, quantifiers
        - :type +d instantiates /all/ quantifiers
        - :type +v is killed off
        That completes the implementation of the propos...
    • syd@cs-syd.eu's avatar
    • Hécate Moonlight's avatar
    • Sylvain Henry's avatar
    • Sylvain Henry's avatar
      Remove sdocWithDynFlags (fix #10143) · a584366b
      Sylvain Henry authored
    • Sylvain Henry's avatar
      Refactor CLabel pretty-printing · 667d6355
      Sylvain Henry authored
      * Don't depend on the selected backend to know if we print Asm or C
        labels: we already have PprStyle to determine this. Moreover even when
        a native backend is used (NCG, LLVM) we may want to C headers
        containing pretty-printed labels, so it wasn't a good predicate
      * Make pretty-printing code clearer and avoid partiality
  4. 23 Sep, 2020 2 commits
  5. 22 Sep, 2020 4 commits
    • Sebastian Graf's avatar
      PmCheck: Rewrite inhabitation test · e9501547
      Sebastian Graf authored
      We used to produce inhabitants of a pattern-match refinement type Nabla
      in the checker in at least two different and mostly redundant ways:
        1. There was `provideEvidence` (now called
           `generateInhabitingPatterns`) which is used by
           `GHC.HsToCore.PmCheck` to produce non-exhaustive patterns, which
           produces inhabitants of a Nabla as a sub-refinement type where all
           match variables are instantiated.
        2. There also was `ensure{,All}Inhabited` (now called
           `inhabitationTest`) which worked slightly different, but was
           whenever new type constraints or negative term constraints were
           added. See below why `provideEvidence` and `ensureAllInhabited`
           can't be the same function, the main reason being performance.
        3. And last but not least there was the `nonVoid` test, which tested
           that a given type was inhabited. We did use this for strict fields
           and -XEmptyCase in the past.
      The overlap of (3) with (2) was always a major pet peeve of mine. The
      latter was quite efficient and proven to work for recursive data types,
      etc, but could not handle negative constraints well (e.g. we often want
      to know if a *refined* type is empty, such as `{ x:[a] | x /= [] }`).
      Lower Your Guards suggested that we could get by with just one, by
      replacing both functions with `inhabitationTest` in this patch.
      That was only possible by implementing the structure of φ constraints
      as in the paper, namely the semantics of φ constructor constraints.
      This has a number of benefits:
        a. Proper handling of unlifted types and strict fields, fixing #18249,
           without any code duplication between
           `GHC.HsToCore.PmCheck.Oracle.instCon` (was `mkOneConFull`) and
        b. `instCon` can perform the `nonVoid` test (3) simply by emitting
           unliftedness constraints for strict fields.
        c. `nonVoid` (3) is thus simply expressed by a call to
        d. Similarly, `ensureAllInhabited` (2), which we called after adding
           type info, now can similarly be expressed as the fuel-based
      See the new `Note [Why inhabitationTest doesn't call generateInhabitingPatterns]`
      why we still have tests (1) and (2).
      Fixes #18249 and brings nice metric decreases for `T17836` (-76%) and
      `T17836b` (-46%), as well as `T18478` (-8%) at the cost of a few very
      minor regressions (< +2%), potentially due to the fact that
      `generateInhabitingPatterns` does more work to suggest the minimal
      COMPLETE set.
      Metric Decrease:
    • Sebastian Graf's avatar
    • Simon Peyton Jones's avatar
      Fix the occurrence analyser · 416bd50e
      Simon Peyton Jones authored
      Ticket #18603 demonstrated that the occurrence analyser's
      handling of
        local RULES for imported Ids
      (which I now call IMP-RULES) was inadequate.  It led the simplifier
      into an infnite loop by failing to label a binder as a loop breaker.
      The main change in this commit is to treat IMP-RULES in a simple and
      uniform way: as extra rules for the local binder.  See
        Note [IMP-RULES: local rules for imported functions]
      This led to quite a bit of refactoring.  The result is still tricky,
      but it's much better than before, and better documented I think.
      Oh, and it fixes the bug.
    • Simon Peyton Jones's avatar
      Better eta-expansion (again) and don't specilise DFuns · 6de40f83
      Simon Peyton Jones authored
      This patch fixes #18223, which made GHC generate an exponential
      amount of code.  There are three quite separate changes in here
      1.  Re-engineer eta-expansion (again).  The eta-expander was
          generating lots of intermediate stuff, which could be optimised
          away, but which choked the simplifier meanwhile.  Relatively
          easy to kill it off at source.
          See Note [The EtaInfo mechanism] in GHC.Core.Opt.Arity.
          The main new thing is the use of pushCoArg in getArg_maybe.
      2.  Stop Specialise specalising DFuns.  This is the cause of a huge
          (and utterly unnecessary) blowup in program size in #18223.
          See Note [Do not specialise DFuns] in GHC.Core.Opt.Specialise.
          I also refactored the Specialise monad a bit... it was silly,
          because it passed on unchanging values as if they were mutable
      3.  Do an extra Simplifer run, after SpecConstra and before
          late-Specialise.  I found (investigating perf/compiler/T16473)
          that failing to do this was crippling *both* SpecConstr *and*
          Specialise.  See Note [Simplify after SpecConstr] in
          This change does mean an extra run of the Simplifier, but only
          with -O2, and I think that's acceptable.
          T16473 allocates *three* times less with this change.  (I changed
          it to check runtime rather than compile time.)
      Some smaller consequences
      * I moved pushCoercion, pushCoArg and friends from SimpleOpt
        to Arity, because it was needed by the new etaInfoApp.
        And pushCoValArg now returns a MCoercion rather than Coercion for
        the argument Coercion.
      * A minor, incidental improvement to Core pretty-printing
      This does fix #18223, (which was otherwise uncompilable. Hooray.  But
      there is still a big intermediate because there are some very deeply
      nested types in that program.
      Modest reductions in compile-time allocation on a couple of benchmarks
          T12425     -2.0%
          T13253    -10.3%
      Metric increase with -O2, due to extra simplifier run
          T9233     +5.8%
          T12227    +1.8%
          T15630    +5.0%
      There is a spurious apparent increase on heap residency on T9630,
      on some architectures at least.  I tried it with -G1 and the residency
      is essentially unchanged.
      Metric Increase
      Metric Decrease
  6. 21 Sep, 2020 4 commits
    • Ben Gamari's avatar
      hadrian: Add extra-deps: happy-1.20 to stack.yaml · aaa51dcf
      Ben Gamari authored
      GHC now requires happy-1.20, which isn't available in LTS-16.14.
      Fixes #18726.
    • Ryan Scott's avatar
      Disallow constraints in KindSigCtxt · 2f222b12
      Ryan Scott authored
      This patch cleans up how `GHC.Tc.Validity` classifies `UserTypeCtxt`s
      that can only refer to kind-level positions, which is important for
      rejecting certain classes of programs. In particular, this patch:
      * Introduces a new `TypeOrKindCtxt` data type and
        `typeOrKindCtxt :: UserTypeCtxt -> TypeOrKindCtxt` function, which
        determines whether a `UserTypeCtxt` can refer to type-level
        contexts, kind-level contexts, or both.
      * Defines the existing `allConstraintsAllowed` and `vdqAllowed`
        functions in terms of `typeOrKindCtxt`, which avoids code
        duplication and ensures that they stay in sync in the future.
      The net effect of this patch is that it fixes #18714, in which it was
      discovered that `allConstraintsAllowed` incorrectly returned `True`
      for `KindSigCtxt`. Because `typeOrKindCtxt` now correctly classifies
      `KindSigCtxt` as a kind-level context, this bug no longer occurs.
    • Ryan Scott's avatar
      Remove unused ThBrackCtxt and ResSigCtxt · 1a0f8243
      Ryan Scott authored
      Fixes #18715.
    • GHC GitLab CI's avatar