Hoogle Search

Within LTS Haskell 24.49 (ghc-9.10.3)

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

  1. package netcode-io

    Bindings to the low-level netcode.io library. Bindings to the low-level netcode.io library, which come in two flavors: c-level bindings and a high-level interface to the library. For the low level interface, refer to the Bindings.Netcode.IO module. For the high-level interface, which is a bit closer to idiomatic Haskell, refer to the Netcode.IO module.

  2. package nettle

    safe nettle binding safe binding for the nettle (http://www.lysator.liu.se/~nisse/nettle/nettle.html) library. Tested with 3.4, might work with 3.2 (but not earlier).

  3. package netwire-input

    Input handling abstractions for netwire This package contains a collection of Monad typeclasses that support interaction with input devices such as keyboard and mice. Moreover, these typeclasses are used to create wires from the netwire package the produce mouse and keyboard input values in a reactive way. This package cannot be used independently and must be used with another package that provides instantiation of these typeclasses such as netwire-input-glfw.

  4. package netwire-input-glfw

    GLFW instance of netwire-input This package contains the necessary glue to allow the use of wires from the netwire-input package. In general, the types associated here should be used only sparingly to plumb the input state through your netwire program. Otherwise, the state should not be modified directly.

  5. package network-conduit-tls

    Create TLS-aware network code with conduits Uses the tls package for a pure-Haskell implementation.

  6. package network-ip

    Internet Protocol data structures This package provides Internet Protocol data structures

  7. package network-multicast

    Simple multicast library The Network.Multicast module is for sending UDP datagrams over multicast (class D) addresses.

  8. package network-uri-template

    Library for parsing and expanding URI Templates, as per RFC 6570 As per the RFC,

    For example, the following URI Template includes a form-style
    parameter expression, as indicated by the "?" operator appearing
    before the variable names.
    
    
    http:/www.example.comfoo{?query,number}
    
    
    The expansion process for expressions beginning with the question-
    mark ("?") operator follows the same pattern as form-style interfaces
    on the World Wide Web:
    
    
    http:/www.example.comfoo{?query,number}
    _____________/
    |
    |
    For each defined variable in [ query, number ],
    substitute "?" if it is the first substitution or "&"
    thereafter, followed by the variable name, '=', and the
    variable's value.
    
    
    If the variables have the values
    
    
    query  := "mycelium"
    number := 100
    
    
    then the expansion of the above URI Template is
    
    
    http:/www.example.comfoo?query=mycelium&number=100
    
    
    Alternatively, if query is undefined, then the expansion would be
    
    
    http:/www.example.comfoo?number=100
    
    
    or if both variables are undefined, then it would be
    
    
    http:/www.example.comfoo
    
    This library handles expanding such templates.

  9. package network-wait

    Lightweight library for waiting on networked services to become available. Please see the README on GitHub at https://github.com/mbg/network-wait#readme

  10. package nfc

    libnfc bindings nfc is a set of bindings to libnfc

Page 222 of many | Previous | Next