Hoogle Search
Within LTS Haskell 24.51 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
pprForall' :: PprFlag flag => ForallVisFlag -> [TyVarBndr flag] -> Cxt -> Doctemplate-haskell Language.Haskell.TH.Ppr No documentation available.
pprForallVis :: [TyVarBndr ()] -> Cxt -> Doctemplate-haskell Language.Haskell.TH.Ppr No documentation available.
-
template-haskell Language.Haskell.TH.Syntax No documentation available.
addForeignFile :: ForeignSrcLang -> String -> Q ()template-haskell Language.Haskell.TH.Syntax Deprecated: Use addForeignSource instead
addForeignFilePath :: ForeignSrcLang -> FilePath -> Q ()template-haskell Language.Haskell.TH.Syntax Same as addForeignSource, but expects to receive a path pointing to the foreign file instead of a String of its contents. Consider using this in conjunction with addTempFile. This is a good alternative to addForeignSource when you are trying to directly link in an object file.
addForeignSource :: ForeignSrcLang -> String -> Q ()template-haskell Language.Haskell.TH.Syntax Emit a foreign file which will be compiled and linked to the object for the current module. Currently only languages that can be compiled with the C compiler are supported, and the flags passed as part of -optc will be also applied to the C compiler invocation that will compile them. Note that for non-C languages (for example C++) extern C directives must be used to get symbols that we can access from Haskell. To get better errors, it is recommended to use #line pragmas when emitting C files, e.g.
{-# LANGUAGE CPP #-} ... addForeignSource LangC $ unlines [ "#line " ++ show (844 + 1) ++ " " ++ show "libraries/template-haskell/Language/Haskell/TH/Syntax.hs" , ... ]qAddForeignFilePath :: Quasi m => ForeignSrcLang -> String -> m ()template-haskell Language.Haskell.TH.Syntax No documentation available.
-
filepath System.OsPath.Types Ifdef around current platform (either WindowsPath or PosixPath).
isLeafOrCollision :: HashMap k v -> Boolunordered-containers Data.HashMap.Internal -
HUnit Test.HUnit.Base Performs a test run with the specified report generators. This handles the actual running of the tests. Most developers will want to use HUnit.Text.runTestTT instead. A developer could use this function to execute tests via another IO system, such as a GUI, or to output the results in a different manner (e.g., upload XML-formatted results to a webservice). Note that the counts in a start report do not include the test case being started, whereas the counts in a problem report do include the test case just finished. The principle is that the counts are sampled only between test case executions. As a result, the number of test case successes always equals the difference of test cases tried and the sum of test case errors and failures.