1. 21 Mar, 2016 14 commits
  2. 20 Mar, 2016 13 commits
  3. 19 Mar, 2016 1 commit
  4. 17 Mar, 2016 4 commits
    • eir@cis.upenn.edu's avatar
      Fix #11512 by getting visibility right for methods · f4f315a3
      eir@cis.upenn.edu authored
      Test case: typecheck/should_compile/T11512
    • eir@cis.upenn.edu's avatar
      Fix #11716. · 3fe87aa0
      eir@cis.upenn.edu authored
      There were several smallish bugs here:
       - We had too small an InScopeSet when rejigging GADT return types.
       - When adding the extra_tvs with a datatype kind signature, we
         were sometimes changing Uniques of an explicitly bound kind var.
       - Using coercionKind in the flattener got the wrong visibility
         for a binder. Now we just zonk to get what we need.
      Test case: dependent/should_compile/RaeJobTalk
    • Csongor Kiss's avatar
      typechecker: fix trac issue #11708 · c5ed41cb
      Csongor Kiss authored and eir@cis.upenn.edu's avatar eir@cis.upenn.edu committed
      Summary: Fixes T11708
      Reviewers: austin, bgamari, goldfire, simonpj
      Reviewed By: goldfire, simonpj
      Subscribers: simonpj, goldfire, thomie
      Differential Revision: https://phabricator.haskell.org/D2006
      GHC Trac Issues: #11708
    • eir@cis.upenn.edu's avatar
      Fix #11711. · b5565f1a
      eir@cis.upenn.edu authored
      There were two bugs here, both simple: we need to filter out
      covars before calling isMetaTyVar in the solver, and TcPat had
      a tcSubType the wrong way round.
      test case: dependent/should_compile/T11711
  5. 16 Mar, 2016 4 commits
    • Erik de Castro Lopo's avatar
      DriverPipeline: Fix 'unused arguments' warnings from Clang · 46f9a476
      Erik de Castro Lopo authored
      When using Clang as the C compiler, over 100 tests were failing
      due to Clang reporting that some command line arguments were not
      being used. These warnings only occur when Clang is compiling
      assembler files which happens in two places, one of which already
      conditionally adding `-Qunused-arguments` to the command line when
      the compiler was Clang. This fixes the other.
      Test Plan: validate with clang as the C compiler
      Reviewers: bgamari, hvr, austin, rwbarton
      Subscribers: thomie
      Differential Revision: https://phabricator.haskell.org/D1998
      GHC Trac Issues: #11684
    • eir@cis.upenn.edu's avatar
      Clean up some pretty-printing in errors. · 5d98b8bf
      eir@cis.upenn.edu authored
      It turns out that there were some pretty egregious mistakes
      in the code that suggested -fprint-explicit-kinds, which are
      fixed. This commit also reorders a bunch of error messages,
      which I think is an improvement.
      This also adds the test case for #11471, which is what
      triggered the cleanup in TcErrors. Now that #11473 is done,
      there is nothing more outstanding for #11471.
      test case: dependent/should_fail/T11471
    • eir@cis.upenn.edu's avatar
      Fix printing of "kind" vs. "type" · f602f4a6
      eir@cis.upenn.edu authored
      This is as reported in #11471, though it's not the focus of that
      test case: polykinds/KindVType
    • eir@cis.upenn.edu's avatar
      Fix #11473. · aade1112
      eir@cis.upenn.edu authored
      I've added a check in the zonker for representation polymorphism.
      I don't like having this be in the zonker, but I don't know where
      else to put it. It can't go in TcValidity, because a clever enough
      user could convince the solver to do bogus representation polymorphism
      even though there's nothing obviously wrong in what they wrote.
      Note that TcValidity doesn't run over *expressions*, which is where
      this problem arises.
      In any case, the check is simple and it works.
      test case: dependent/should_fail/T11473
  6. 15 Mar, 2016 4 commits