Hoogle Search

Within LTS Haskell 24.6 (ghc-9.10.2)

Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.

  1. InteractiveName :: GetDocsFailure

    ghc-lib GHC.Runtime.Eval

    The Name was defined interactively.

  2. type InteractiveValidator = Value -> IO Either String Value

    minimal-configuration System.Config.File

    Via the Left data constructor we are able to pass the message necessary to notify the user that the inputed data is not valid

  3. module Numeric.Uncertain.Correlated.Interactive

    Exports all of the interface of Numeric.Uncertain.Correlated, except meant to be run in a ghci session "interactively" for exploratory purposes, or in a plain IO action (instead of inside a Corr monad). For example, with the Numeric.Uncertain.Correlated interface:

    ghci> evalCorr $ do
    x <- sampleUncert $ 12.5 +/- 0.8
    y <- sampleUncert $ 15.9 +/- 0.5
    z <- sampleUncert $ 1.52 +/- 0.07
    let k = y**x
    resolveUncert $ (x+z) * logBase z k
    1200 +/- 200
    
    And with the interface from this "interactive" module:
    ghci> x <- sampleUncert $ 12.5 +/- 0.8
    ghci> y <- sampleUncert $ 15.9 +/- 0.5
    ghci> z <- sampleUncert $ 1.52 +/- 0.07
    ghci> let k = y**x
    ghci> resolveUncert $ (x+z) * logBase z k
    1200 +/- 200
    
    The main purpose of this module is to allow one to use ghci as a fancy "calculator" for computing and exploring propagated uncertainties of complex and potentially correlated samples with uncertainty. Because many of the names overlap with the names from the Numeric.Uncertain.Correlated module, it is recommended that you never have both imported at the same time in ghci or in a file, or import them qualified if you must. Also note that all of these methods only work with Uncert Doubles, and are not polymorphic over different numeric types. Be aware that this module is not robustly tested in heavily concurrent situations/applications.

  4. runInteractiveCommand :: String -> IO (Handle, Handle, Handle, ProcessHandle)

    process System.Process

    Runs a command using the shell, and returns Handles that may be used to communicate with the process via its stdin, stdout, and stderr respectively.

  5. runInteractiveProcess :: FilePath -> [String] -> Maybe FilePath -> Maybe [(String, String)] -> IO (Handle, Handle, Handle, ProcessHandle)

    process System.Process

    Runs a raw command, and returns Handles that may be used to communicate with the process via its stdin, stdout and stderr respectively. For example, to start a process and feed a string to its stdin:

    (inp,out,err,pid) <- runInteractiveProcess "..."
    forkIO (hPutStr inp str)
    

  6. runInteractiveProcess_lock :: MVar ()

    process System.Process.Internals

    runInteractiveProcess blocks signals around the fork(). Since blocking/unblocking of signals is a global state operation, we need to ensure mutual exclusion of calls to runInteractiveProcess. This lock is exported so that other libraries which also need to fork() (and also need to make the same global state changes) can protect their changes with the same lock. See https://github.com/haskell/process/pull/154.

  7. GhcModeInteractive :: GhcMode

    Cabal Distribution.Simple.Program.GHC

    ghci / ghc --interactive

  8. getInteractiveDynFlags :: GhcMonad m => m DynFlags

    ghc GHC

    Get the DynFlags used to evaluate interactive expressions.

  9. runTcInteractive :: HscEnv -> TcRn a -> IO (Messages TcRnMessage, Maybe a)

    ghc GHC

    No documentation available.

  10. setInteractiveDynFlags :: GhcMonad m => DynFlags -> m ()

    ghc GHC

    Set the DynFlags used to evaluate interactive expressions. Also initialise (load) plugins. Note: this cannot be used for changes to packages. Use setSessionDynFlags, or setProgramDynFlags and then copy the unitState into the interactive DynFlags.

Page 16 of many | Previous | Next