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.

Exact lookup

1. newtype Step_Properties

   gogol-dataflow	Gogol.Dataflow.Types

   Named properties associated with the step. Each kind of predefined step has its own required set of properties. Must be provided on Create. Only retrieved with JOBVIEWALL. See: newStep_Properties smart constructor.

2. Step_Properties :: HashMap Text Value -> Step_Properties

   gogol-dataflow	Gogol.Dataflow.Types

   No documentation available.

3. ghciStepIO :: GHCiSandboxIO m => m a -> IO a

   base	GHC.GHCi

   No documentation available.

4. type BuildStep a = BufferRange -> IO BuildSignal a

   bytestring	Data.ByteString.Builder.Internal

   BuildSteps may be called *multiple times* and they must not rise an async. exception.

5. buildStepToCIOS :: AllocationStrategy -> BuildStep a -> IO (ChunkIOStream a)

   bytestring	Data.ByteString.Builder.Internal

   Convert a BuildStep to a ChunkIOStream stream by executing it on Buffers allocated according to the given AllocationStrategy.

6. fillWithBuildStep :: BuildStep a -> (Ptr Word8 -> a -> IO b) -> (Ptr Word8 -> Int -> BuildStep a -> IO b) -> (Ptr Word8 -> StrictByteString -> BuildStep a -> IO b) -> BufferRange -> IO b

   bytestring	Data.ByteString.Builder.Internal

   Fill a BufferRange using a BuildStep.

7. finalBuildStep :: BuildStep ()

   bytestring	Data.ByteString.Builder.Internal

   The final build step that returns the done signal.

8. testCaseSteps :: TestName -> ((String -> IO ()) -> Assertion) -> TestTree

   tasty-hunit	Test.Tasty.HUnit

   Create a multi-step unit test. Example:

   main = defaultMain $ testCaseSteps "Multi-step test" $ \step -> do
   step "Preparing..."
   -- do something
   
   step "Running part 1"
   -- do something
   
   step "Running part 2"
   -- do something
   assertFailure "BAM!"
   
   step "Running part 3"
   -- do something
   

   The step calls are mere annotations. They let you see which steps were performed successfully, and which step failed. You can think of step as putStrLn, except putStrLn would mess up the output with the console reporter and get lost with the others. For the example above, the output will be

   Multi-step test: FAIL
   Preparing...
   Running part 1
   Running part 2
   BAM!
   
   1 out of 1 tests failed (0.00s)
   

   Note that:
   • Tasty still treats this as a single test, even though it consists of multiple steps.
   • The execution stops after the first failure. When we are looking at a failed test, we know that all displayed steps but the last one were successful, and the last one failed. The steps after the failed one are not displayed, since they didn't run.

9. LStep :: Leftmost a -> Leftmost a

   lens	Control.Lens.Internal.Fold

   No documentation available.

10. RStep :: Rightmost a -> Rightmost a

    lens	Control.Lens.Internal.Fold

    No documentation available.

Page 39 of many | Previous | Next