Hoogle Search

Within LTS Haskell 24.39 (ghc-9.10.3)

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

Exact lookup

1. module RIO.List.Partial

   List partial functions. Import as:

   import qualified RIO.List.Partial as L'
   

2. module RIO.Map.Partial

   Strict Map partial functions. Import as:

   import qualified RIO.Map.Partial as Map'
   

3. module RIO.NonEmpty.Partial

   NonEmpty list partial functions. Import as:

   import qualified RIO.NonEmpty.Partial as NE'
   

4. module RIO.Partial

   Partial functions. Import as:

   import qualified RIO.Partial as RIO'
   

5. module RIO.Prelude

   No documentation available.

6. class Monad m => PrimMonad (m :: Type -> Type)

   rio	RIO.Prelude.Types

   Class of monads which can perform primitive state-transformer actions.

7. data Proxy (t :: k)

   rio	RIO.Prelude.Types

   Proxy is a type that holds no data, but has a phantom parameter of arbitrary type (or even kind). Its use is to provide type information, even though there is no value available of that type (or it may be too costly to create one). Historically, Proxy :: Proxy a is a safer alternative to the undefined :: a idiom.

   >>> Proxy :: Proxy (Void, Int -> Int)
   Proxy
   

   Proxy can even hold types of higher kinds,

   >>> Proxy :: Proxy Either
   Proxy
   

   >>> Proxy :: Proxy Functor
   Proxy
   

   >>> Proxy :: Proxy complicatedStructure
   Proxy
   

8. Proxy :: Proxy (t :: k)

   rio	RIO.Prelude.Types

   No documentation available.

9. module RIO.Process

   Interacting with external processes. This module provides a layer on top of System.Process.Typed, with the following additions:

   • For efficiency, it will cache PATH lookups.
   • For convenience, you can set the working directory and env vars overrides in a RIO environment instead of on the individual calls to the process.
   • Built-in support for logging at the debug level.
   In order to switch over to this API, the main idea is:
   • Like most of the rio library, you need to create an environment value (this time ProcessContext), and include it in your RIO environment. See mkProcessContext.
   • Instead of using the proc function from System.Process.Typed for creating a ProcessConfig, use the locally defined proc function, which will handle overriding environment variables, looking up paths, performing logging, etc.
   Once you have your ProcessConfig, use the standard functions from Typed (reexported here for convenient) for running the ProcessConfig.

10. PathsInvalidInPath :: [FilePath] -> ProcessException

    rio	RIO.Process

    No documentation available.

Page 272 of many | Previous | Next