Hoogle Search
Within LTS Haskell 24.67 (ghc-9.10.3)
Note that Stackage only displays results for the latest LTS and Nightly snapshot. Learn more.
setState# :: BufferCodec from to state -> state -> IO ()ghc-internal GHC.Internal.IO.Encoding.Types No documentation available.
setNonBlockingMode :: FD -> Bool -> IO FDghc-internal GHC.Internal.IO.FD No documentation available.
setState# :: BufferCodec from to state -> state -> IO ()ghc-internal GHC.Internal.IO.Handle.Types No documentation available.
setAffinity :: ParFlags -> Boolghc-internal GHC.Internal.RTS.Flags No documentation available.
setEnv :: String -> String -> IO ()ghc-internal GHC.Internal.System.Environment setEnv name value sets the specified environment variable to value. Early versions of this function operated under the mistaken belief that setting an environment variable to the empty string on Windows removes that environment variable from the environment. For the sake of compatibility, it adopted that behavior on POSIX. In particular
setEnv name ""
has the same effect asunsetEnv name
If you'd like to be able to set environment variables to blank strings, use setEnv. Throws IOException if name is the empty string or contains an equals sign. Beware that this function must not be executed concurrently with getEnv, lookupEnv, getEnvironment and such. One thread reading environment variables at the same time with another one modifying them can result in a segfault, see Setenv is not Thread Safe for discussion.setEnv :: String -> String -> Bool -> IO ()ghc-internal GHC.Internal.System.Environment.Blank Like setEnv, but allows blank environment values and mimics the function signature of setEnv from the unix package. Beware that this function must not be executed concurrently with getEnv, lookupEnv, getEnvironment and such. One thread reading environment variables at the same time with another one modifying them can result in a segfault, see Setenv is not Thread Safe for discussion.
setAllocationCounter :: Int64 -> IO ()ghc-internal GHC.Internal.System.Mem Every thread has an allocation counter that tracks how much memory has been allocated by the thread. The counter is initialized to zero, and setAllocationCounter sets the current value. The allocation counter counts *down*, so in the absence of a call to setAllocationCounter its value is the negation of the number of bytes of memory allocated by the thread. There are two things that you can do with this counter:
- Use it as a simple profiling mechanism, with getAllocationCounter.
- Use it as a resource limit. See enableAllocationLimit.
-
ghc-internal GHC.Internal.System.Posix.Internals No documentation available.
setCooked :: FD -> Bool -> IO ()ghc-internal GHC.Internal.System.Posix.Internals No documentation available.
setEcho :: FD -> Bool -> IO ()ghc-internal GHC.Internal.System.Posix.Internals No documentation available.