Hoogle Search

Within LTS Haskell 24.3 (ghc-9.10.2)

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

  1. package netlib-ffi

    Helper modules for FFI to BLAS and LAPACK Netlib is a collection of packages for efficient numeric linear algebra. Most prominent parts of Netlib are BLAS and LAPACK. These packages contain functions for matrix computations, solution of simultaneous linear equations and eigenvalue problems. This package provides definitions shared by the packages blas-ffi and lapack-ffi.

  2. package network-transport

    Network abstraction layer Network.Transport is a Network Abstraction Layer which provides the following high-level concepts: . * Nodes in the network are represented by EndPoints. These are heavyweight stateful objects. . * Each EndPoint has an EndPointAddress. . * Connections can be established from one EndPoint to another using the EndPointAddress of the remote end. . * The EndPointAddress can be serialised and sent over the network, whereas EndPoints and connections cannot. . * Connections between EndPoints are unidirectional and lightweight. . * Outgoing messages are sent via a Connection object that represents the sending end of the connection. . * Incoming messages for all of the incoming connections on an EndPoint are collected via a shared receive queue. . * In addition to incoming messages, EndPoints are notified of other Events such as new connections or broken connections. . This design was heavily influenced by the design of the Common Communication Interface (http://www.olcf.ornl.gov/center-projects/common-communication-interface). Important design goals are: . * Connections should be lightweight: it should be no problem to create thousands of connections between endpoints. . * Error handling is explicit: every function declares as part of its type which errors it can return (no exceptions are thrown) . * Error handling is "abstract": errors that originate from implementation specific problems (such as "no more sockets" in the TCP implementation) get mapped to generic errors ("insufficient resources") at the Transport level. . This package provides the generic interface only; you will probably also want to install at least one transport implementation (network-transport-*).

  3. package os-string

    Library for manipulating Operating system strings. This package provides functionality for manipulating OsString values, and is shipped with GHC.

  4. package relude

    Safe, performant, user-friendly and lightweight Haskell Standard Library relude is an alternative prelude library. If you find the default Prelude unsatisfying, despite its advantages, consider using relude instead.

    Relude goals and design principles

    • Productivity. You can be more productive with a "non-standard" standard library, and relude helps you with writing safer and more efficient code faster.
    • Total programming. Usage of partial functions can lead to unexpected bugs and runtime exceptions in pure code. The types of partial functions lie about their behaviour. And even if it is not always possible to rely only on total functions, relude strives to encourage best-practices and reduce the chances of introducing a bug.TODO: table
    • Type-safety. We use the "make invalid states unrepresentable" motto as one of our guiding principles. If it is possible, we express this concept through the types.Example: whenNotNull :: Applicative f => [a] -> (NonEmpty a -> f ()) -> f ()
    • Performance. We prefer Text over String, use space-leaks-free functions (e.g. our custom performant sum and product), introduce {-# INLINE #-} and {-# SPECIALIZE #-} pragmas where appropriate, and make efficient container types (e.g. Map, HashMap, Set) more accessible.
    • Minimalism (low number of dependencies). We do not force users of relude to stick to any specific lens or text formatting or logging library. Where possible, relude depends only on boot libraries. The Dependency graph of relude can give you a clearer picture.
    • Convenience. Despite minimalism, we want to bring commonly used types and functions into scope, and make available functions easier to use. Some examples of conveniences:
      1. No need to add containers, unordered-containers, text and bytestring to dependencies in your .cabal file to use the main API of these libraries
      2. No need to import types like NonEmpty, Text, Set, Reader[T], MVar, STM
      3. Functions like liftIO, fromMaybe, sortWith are available by default as well
      4. IO actions are lifted to MonadIO
    • Excellent documentation.
      1. Tutorial
      2. Migration guide from Prelude
      3. Haddock for every function with examples tested by doctest.
      4. Documentation regarding internal module structure
      5. relude-specific HLint rules: .hlint.yaml
    • User-friendliness. Anyone should be able to quickly migrate to relude. Only some basic familiarity with the common libraries like text and containers should be enough (but not necessary).
    • Exploration. We have space to experiment with new ideas and proposals without introducing breaking changes. relude uses the approach with Extra.* modules which are not exported by default. The chosen approach makes it quite easy for us to provide new functionality without breaking anything and let the users decide to use it or not.

  5. package selective

    Selective applicative functors Selective applicative functors: declare your effects statically, select which to execute dynamically. This is a library for selective applicative functors, or just selective functors for short, an abstraction between applicative functors and monads, introduced in this paper.

  6. package storable-complex

    Storable instance for Complex Provides a Storable instance for Complex which is binary compatible with C99, C++ and Fortran complex data types. The only purpose of this package is to provide a standard location for this instance so that other packages needing this instance can play nicely together.

  7. package th-compat

    Backward- (and forward-)compatible Quote and Code types This package defines a Language.Haskell.TH.Syntax.Compat module, which backports the Quote and Code types to work across a wide range of template-haskell versions. The makeRelativeToProject utility is also backported. On recent versions of template-haskell (2.17.0.0 or later), this module simply reexports definitions from Language.Haskell.TH.Syntax. Refer to the Haddocks for Language.Haskell.TH.Syntax.Compat for examples of how to use this module.

  8. package auto-update

    Efficiently run periodic, on-demand actions API docs and the README are available at http://www.stackage.org/package/auto-update.

  9. package data-binary-ieee754

    Parser/Serialiser for IEEE-754 floating-point values Convert Float and Decimal values to/from raw octets.

  10. package diagrams-core

    Core libraries for diagrams EDSL The core modules underlying diagrams, an embedded domain-specific language for compositional, declarative drawing.

Page 29 of many | Previous | Next