1. 18 Jun, 2012 1 commit
  2. 15 Jun, 2012 1 commit
  3. 14 Jun, 2012 2 commits
  4. 12 Jun, 2012 2 commits
    • Ross Paterson's avatar
      tweak documentation of mdo/rec · 96a37685
      Ross Paterson authored
      96a37685
    • Simon Peyton Jones's avatar
      Revive 'mdo' expressions, per discussion in Trac #4148 · 4f8e86b4
      Simon Peyton Jones authored
      Summary:
        - mdo expressions are enabled by RecursiveDo pragma
      
        - mdo expressions perform full segmentation
      
        - 'rec' groups inside 'do' are changed so they do *not*
          perform any segmentation.
      
        - Both 'mdo' and 'rec' are enabled by 'RecursiveDo'
          'DoRec' is deprecated in favour of 'RecursiveDo'
          (The 'rec' keyword is also enabled by 'Arrows', as now.)
      
      Thanks to Levent for doing all the work
      4f8e86b4
  5. 07 Jun, 2012 2 commits
    • Simon Peyton Jones's avatar
      Support polymorphic kind recursion · c9117200
      Simon Peyton Jones authored
      This is (I hope) the last major patch for kind polymorphism.
      The big new feature is polymorphic kind recursion when you
      supply a complete kind signature for a type constructor.
      (I've documented it in the user manual too.)
      
      This fixes Trac #6137, #6093, #6049.
      
      The patch also makes type/data families less polymorphic by default.
         data family T a
      now defaults to T :: * -> *
      If you want T :: forall k. k -> *, use
         data family T (a :: k)
      
      This defaulting to * is done whenever there is a
      "complete, user-specified kind signature", something that is
      carefully defined in the user manual.
      
      Hurrah!
      c9117200
    • Simon Peyton Jones's avatar
  6. 15 May, 2012 2 commits
    • pcapriotti's avatar
      Simplify the behavior of package db flags. · ba409e30
      pcapriotti authored
      Previously, the `-no-user-package` and `-no-global-package` flags
      affected the "initial" stack only, while `user-package` and
      `global-packages` appended to the end of the stack.
      
      This commit changes the behavior of those flags, so that they are always
      applied to the stack as a whole.
      
      The effect of the GHC_PACKAGE_PATH environment variable has also been
      changed: terminating it with a separator now adds the default package
      dbs (user and global) instead of the initial stack.
      ba409e30
    • pcapriotti's avatar
      Update documentation of the package db flags. · 2fe15464
      pcapriotti authored
      2fe15464
  7. 30 Apr, 2012 1 commit
  8. 27 Apr, 2012 2 commits
  9. 26 Apr, 2012 1 commit
  10. 12 Apr, 2012 2 commits
  11. 11 Apr, 2012 2 commits
  12. 04 Apr, 2012 1 commit
  13. 31 Mar, 2012 2 commits
  14. 30 Mar, 2012 1 commit
  15. 28 Mar, 2012 1 commit
  16. 23 Mar, 2012 6 commits
  17. 22 Mar, 2012 1 commit
  18. 16 Mar, 2012 1 commit
  19. 09 Mar, 2012 1 commit
  20. 01 Mar, 2012 1 commit
    • Simon Marlow's avatar
      GHCi: add :seti, for options that apply only at the prompt (#3217) · 2e55760b
      Simon Marlow authored
      GHCi now maintains two DynFlags: one that applies to whole modules
      loaded with :load, and one that applies to things typed at the prompt
      (expressions, statements, declarations, commands).
      
        The :set command modifies both DynFlags.  This is for backwards
        compatibility: users won't notice any difference.
      
        The :seti command applies only to the interactive DynFlags.
      
      Additionally, I made a few changes to ":set" (with no arguments):
      
        * Now it only prints out options that differ from the defaults,
          rather than the whole list.
      
        * There is a new variant, ":set -a" to print out all options (the
          old behaviour).
      
        * It also prints out language options.
      
      e.g.
      
      Prelude> :set
      options currently set: none.
      base language is: Haskell2010
      with the following modifiers:
        -XNoDatatypeContexts
        -XNondecreasingIndentation
      GHCi-specific dynamic flag settings:
      other dynamic, non-language, flag settings:
        -fimplicit-import-qualified
      warning settings:
      
      ":seti" (with no arguments) does the same as ":set", but for the
      interactive options.  It also has the "-a" option.
      
      The interactive DynFlags are kept in the InteractiveContext, and
      copied into the HscEnv at the appropriate points (all in HscMain).
      
      There are some new GHC API operations:
      
      -- | Set the 'DynFlags' used to evaluate interactive expressions.
      setInteractiveDynFlags :: GhcMonad m => DynFlags -> m ()
      
      -- | Get the 'DynFlags' used to evaluate interactive expressions.
      getInteractiveDynFlags :: GhcMonad m => m DynFlags
      
      -- | Sets the program 'DynFlags'.
      setProgramDynFlags :: GhcMonad m => DynFlags -> m [PackageId]
      
      -- | Returns the program 'DynFlags'.
      getProgramDynFlags :: GhcMonad m => m DynFlags
      
      Note I have not completed the whole of the plan outlined in #3217 yet:
      when in the context of a loaded module we don't take the interactive
      DynFlags from that module.  That needs some more refactoring and
      thinking about, because we'll need to save and restore the original
      interactive DynFlags.
      
      This solves the immediate problem that people are having with the new
      flag checking in 7.4.1, because now it is possible to set language
      options in ~/.ghci that do not affect loaded modules and thereby cause
      recompilation.
      2e55760b
  21. 27 Feb, 2012 4 commits
  22. 26 Feb, 2012 1 commit
    • Ian Lynagh's avatar
      Implement "value" imports with the CAPI · ae04bd43
      Ian Lynagh authored
      This allows us to import values (i.e. non-functions) with the CAPI.
      This means we can access values even if (on some or all platforms)
      they are simple #defines.
      ae04bd43
  23. 22 Feb, 2012 1 commit
  24. 17 Feb, 2012 1 commit