Hoogle Search

Within LTS Haskell 24.34 (ghc-9.10.3)

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

  1. data ChecksumType

    gi-glib GI.GLib.Enums

    The hashing algorithm to be used by Checksum when performing the digest of some data. Note that the ChecksumType enumeration may be extended at a later date to include new hashing algorithm types. Since: 2.16

  2. ChecksumTypeMd5 :: ChecksumType

    gi-glib GI.GLib.Enums

    Use the MD5 hashing algorithm

  3. ChecksumTypeSha1 :: ChecksumType

    gi-glib GI.GLib.Enums

    Use the SHA-1 hashing algorithm

  4. ChecksumTypeSha256 :: ChecksumType

    gi-glib GI.GLib.Enums

    Use the SHA-256 hashing algorithm

  5. ChecksumTypeSha384 :: ChecksumType

    gi-glib GI.GLib.Enums

    Use the SHA-384 hashing algorithm (Since: 2.51)

  6. ChecksumTypeSha512 :: ChecksumType

    gi-glib GI.GLib.Enums

    Use the SHA-512 hashing algorithm (Since: 2.36)

  7. computeChecksumForBytes :: (HasCallStack, MonadIO m) => ChecksumType -> Bytes -> m (Maybe Text)

    gi-glib GI.GLib.Functions

    Computes the checksum for a binary data. This is a convenience wrapper for checksumNew, checksumGetString and checksumFree. The hexadecimal string returned will be in lower case. Since: 2.34

  8. computeChecksumForData :: (HasCallStack, MonadIO m) => ChecksumType -> ByteString -> m (Maybe Text)

    gi-glib GI.GLib.Functions

    Computes the checksum for a binary data of length. This is a convenience wrapper for checksumNew, checksumGetString and checksumFree. The hexadecimal string returned will be in lower case. Since: 2.16

  9. computeChecksumForString :: (HasCallStack, MonadIO m) => ChecksumType -> Text -> Int64 -> m (Maybe Text)

    gi-glib GI.GLib.Functions

    Computes the checksum of a string. The hexadecimal string returned will be in lower case. Since: 2.16

  10. testSummary :: (HasCallStack, MonadIO m) => Text -> m ()

    gi-glib GI.GLib.Functions

    Set the summary for a test, which describes what the test checks, and how it goes about checking it. This may be included in test report output, and is useful documentation for anyone reading the source code or modifying a test in future. It must be a single line. This should be called at the top of a test function. For example:

    C code

    static void
test_array_sort (void)
{
g_test_summary ("Test my_array_sort() sorts the array correctly and stably, "
"including testing zero length and one-element arrays.");

…
}
    Since: 2.62

Page 102 of many | Previous | Next