Hoogle Search

Within LTS Haskell 24.9 (ghc-9.10.2)

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

  1. AllServerAttributes :: ServerAttributeGroup

    OpenGL Graphics.Rendering.OpenGL.GL.SavingState

    No documentation available.

  2. type AllowEvents = CInt

    X11 Graphics.X11.Types

    No documentation available.

  3. type AllowExposuresMode = CInt

    X11 Graphics.X11.Xlib.Misc

    No documentation available.

  4. data AllocationLimitExceeded

    ghc-internal GHC.Internal.Control.Exception

    This thread has exceeded its allocation limit. See setAllocationCounter and enableAllocationLimit.

  5. AllocationLimitExceeded :: AllocationLimitExceeded

    ghc-internal GHC.Internal.Control.Exception

    No documentation available.

  6. data AllocationLimitExceeded

    ghc-internal GHC.Internal.Control.Exception.Base

    This thread has exceeded its allocation limit. See setAllocationCounter and enableAllocationLimit.

  7. AllocationLimitExceeded :: AllocationLimitExceeded

    ghc-internal GHC.Internal.Control.Exception.Base

    No documentation available.

  8. module GHC.Internal.Foreign.Marshal.Alloc

    The module Foreign.Marshal.Alloc provides operations to allocate and deallocate blocks of raw memory (i.e., unstructured chunks of memory outside of the area maintained by the Haskell storage manager). These memory blocks are commonly used to pass compound data structures to foreign functions or to provide space in which compound result values are obtained from foreign functions. If any of the allocation functions fails, an exception is thrown. In some cases, memory exhaustion may mean the process is terminated. If free or reallocBytes is applied to a memory area that has been allocated with alloca or allocaBytes, the behaviour is undefined. Any further access to memory areas allocated with alloca or allocaBytes, after the computation that was passed to the allocation function has terminated, leads to undefined behaviour. Any further access to the memory area referenced by a pointer passed to realloc, reallocBytes, or free entails undefined behaviour. All storage allocated by functions that allocate based on a size in bytes must be sufficiently aligned for any of the basic foreign types that fits into the newly allocated storage. All storage allocated by functions that allocate based on a specific type must be sufficiently aligned for that type. Array allocation routines need to obey the same alignment constraints for each array element. The underlying implementation is wrapping the stdlib.h malloc, realloc, and free. In other words it should be safe to allocate using C-malloc, and free memory with free from this module.

  9. data AllocationLimitExceeded

    ghc-internal GHC.Internal.IO.Exception

    This thread has exceeded its allocation limit. See setAllocationCounter and enableAllocationLimit.

  10. AllocationLimitExceeded :: AllocationLimitExceeded

    ghc-internal GHC.Internal.IO.Exception

    No documentation available.

Page 39 of many | Previous | Next