Hoogle Search

Within LTS Haskell 24.52 (ghc-9.10.3)

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

Exact lookup

1. gcdetails_allocated_bytes :: GCDetails -> Word64

   ghc-internal	GHC.Internal.Stats

   Number of bytes allocated since the previous GC

2. disableAllocationLimit :: IO ()

   ghc-internal	GHC.Internal.System.Mem

   Disable allocation limit processing for the current thread.

3. enableAllocationLimit :: IO ()

   ghc-internal	GHC.Internal.System.Mem

   Enables the allocation counter to be treated as a limit for the current thread. When the allocation limit is enabled, if the allocation counter counts down below zero, the thread will be sent the AllocationLimitExceeded asynchronous exception. When this happens, the counter is reinitialised (by default to 100K, but tunable with the +RTS -xq option) so that it can handle the exception and perform any necessary clean up. If it exhausts this additional allowance, another AllocationLimitExceeded exception is sent, and so forth. Like other asynchronous exceptions, the AllocationLimitExceeded exception is deferred while the thread is inside mask or an exception handler in catch. Note that memory allocation is unrelated to live memory, also known as heap residency. A thread can allocate a large amount of memory and retain anything between none and all of it. It is better to think of the allocation limit as a limit on CPU time, rather than a limit on memory. Compared to using timeouts, allocation limits don't count time spent blocked or in foreign calls.

4. getAllocationCounter :: IO Int64

   ghc-internal	GHC.Internal.System.Mem

   Return the current value of the allocation counter for the current thread.

5. 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.
   Allocation accounting is accurate only to about 4Kbytes.

6. module GI.Pango.Callbacks

   No documentation available.

7. type AttrClassCopyFieldCallback = Attribute -> IO Attribute

   gi-pango	GI.Pango.Callbacks

   No description available in the introspection data.

8. type AttrClassDestroyFieldCallback = Attribute -> IO ()

   gi-pango	GI.Pango.Callbacks

   No description available in the introspection data.

9. type AttrClassEqualFieldCallback = Attribute -> Attribute -> IO Bool

   gi-pango	GI.Pango.Callbacks

   No description available in the introspection data.

10. type C_AttrClassCopyFieldCallback = Ptr Attribute -> IO Ptr Attribute

    gi-pango	GI.Pango.Callbacks

    Type for the callback on the (unwrapped) C side.

Page 503 of many | Previous | Next