The numhask package

[ Tags: bsd3, library, mathematics ] [ Propose Tags ]

A numeric prelude, providing a clean structure for numbers and operations that combine them.

[Skip to Readme]


Versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.1.0, 0.1.1, 0.1.2, 0.1.3,
Dependencies base (>=4.7 && <4.11), protolude (>=0.1 && <0.3), QuickCheck (>=2.8 && <3), tasty, tasty-quickcheck [details]
License BSD3
Copyright Tony Day
Author Tony Day
Category mathematics
Home page
Bug tracker
Source repository head: git clone
Uploaded Wed Dec 27 06:03:05 UTC 2017 by tonyday567
Distributions LTSHaskell:, NixOS:, Stackage:, Tumbleweed:
Downloads 2085 total (1021 in the last 30 days)
Rating 2.0 (votes: 1) [estimated by rule of succession]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2017-12-27 [all 1 reports]
Hackage Matrix CI




Maintainer's Corner

For package maintainers and hackage trustees

Readme for numhask-

[back to package description]


Build Status Hackage lts nightly

A numeric prelude, providing a clean structure for numbers and operations that combine them.

Field heirarchy

Field Hierarchy

Numbers with structure

Hilbert Hierarchy

This particular shed has been painted:

  • by providing separately named magma-derived classes for addition and multiplication, and then being symetrical in the treatment of the two heirarchies. A short magma structure is provided with the intention of supplying appropriate classes fro operators that are no addition nor multiplication, but this structure is not hooked up to the main classes.
  • to be as compatible as practical with the existing haskell ecosystem. Ints, Integers, Floats, Doubles and Complex are taken from base and given numhask instances, so they are also Num instances. Monoid and Semigroup are not used in numhask to maintain compatability.
  • as a replacement for anything in base that has a Num, Fractional or Real constraint.
  • includes QuickCheck tests of the numeric laws implicit in the classes. This also includes tracking where laws are approximate or fail for non-exact numbers.
  • the usual operators (+) and (*) operators are reserved for commutative relationships, with plus and times being used for non-commutative ones.

Alternative color-schemes, stylistic flourishes and opines are welcome.

In summary, the library doesn't do anything fancy. But if having to define (*) when you just want a (+) offends your sensibilities, it may bring some sanity.


{-# LANGUAGE NoImplicitPrelude #-}
import Numhask.Prelude

'Numhask.Prelude' is designed as a drop-in replacement for Prelude and 'NoImplicitPrelude' is obligatory. Behind the scenes, the module wraps protolude.

See Examples for basic examples, numhask-array for numbers with structure, and numhask-range for slightly heavier number crunching.