This project is mirrored from Pull mirroring updated .
  1. 21 Jul, 2017 1 commit
  2. 20 Jul, 2017 3 commits
    • Francesco Gazzetta's avatar
      Remove polymorphism from runProjectPreBuildPhase · 484bb6cb
      Francesco Gazzetta authored
      Return a monomorphic TargetsMap from selectPlanSubset and put it in the
      final ProjectBuildContext.
      This causes slight duplication in CmdRun.hs, but not as bas as when we
      didn't return anything. In exchange, the final return type is much
      Note that CmdConfigure returns an empty TargetsMap, as configure doesn't
      accept targets.
    • Francesco Gazzetta's avatar
      Reduce duplication in CmdRun · 7ea22b0f
      Francesco Gazzetta authored
      Previously, the extraction of the target from the targetStrings was done
      twice: inside the function passed to 'runProjectPreBuildPhase' and right
      after it.
      Now 'runProjectPreBuildPhase' is able to return information from that
      function, and the duplication was removed, along with some assumptions
      about the number of targets.
    • Mikhail Glushenkov's avatar
      Formatting. · bc8daa74
      Mikhail Glushenkov authored
      [ci skip]
  3. 19 Jul, 2017 1 commit
  4. 18 Jul, 2017 1 commit
  5. 17 Jul, 2017 1 commit
  6. 16 Jul, 2017 1 commit
  7. 15 Jul, 2017 4 commits
  8. 14 Jul, 2017 1 commit
  9. 10 Jul, 2017 1 commit
  10. 07 Jul, 2017 1 commit
  11. 05 Jul, 2017 1 commit
  12. 04 Jul, 2017 5 commits
  13. 03 Jul, 2017 8 commits
  14. 02 Jul, 2017 2 commits
  15. 04 Jun, 2017 1 commit
  16. 19 May, 2017 3 commits
  17. 18 May, 2017 1 commit
    • Herbert Valerio Riedel's avatar
      Remove --allow-{newer,older} support from Cabal · a95b8f4e
      Herbert Valerio Riedel authored
      This is a preparatory refactoring needed for future work such as #4203.
      I've refrained from doing additional cleanups in order to keep this a
      refactoring that mostly moves around blocks of code mostly
      unchanged (except for whitespace), and make it easier to review.
      This feature was originally implemented because its lack was complained
      about by Stack/Stackage developers. However, after it got implemented it
      was never really being used; what's more, it's causing us overhead for
      no benefit as well as blocking us improving the implementation via the
      likes of #4203.
      Closes #3581
  18. 15 May, 2017 1 commit
  19. 09 May, 2017 1 commit
    • Edward Z. Yang's avatar
      Fix for-hackage rendering to distinguish NoFlag and default case. · a3877791
      Edward Z. Yang authored
      This commit fixes one instances of a general bug where noFlag
      command line flags do not translate correctly when converted
      into the field description format (and in fact, cannot be
      converted correctly.)
      The bug goes something like this:
      1. A noArg command line parser translates into a "choice"
         command line parser, for which there is only one choice
         (the flag that would be set when you toggle it on.)
      2. Choice command line parsers get translated into the field
         format by having a rendering for each defined choice,
         and then default to empty (omit the field entirely) if
         no choices apply.
      3. This means that NoFlag and the "default choice" (if you
         hadn't specified the flag at all) render identically,
         because there is never a choice for the default choice
         in the no arg field.
      In the interest of getting this to work, I manually made
      for-hackage work correctly, but there is probably a way to
      refactor this into a more universal fix.
      CC @dcoutts
      Signed-off-by: default avatarEdward Z. Yang <>
  20. 08 May, 2017 1 commit
  21. 06 May, 2017 1 commit