ghc-typelits-knownnat
What is ghc-typelits-knownnat?
A type checker plugin for GHC that can derive "complex" KnownNat constraints from other simple/variable KnownNat constraints. i.e. without this plugin, you must have both a KnownNat n and a KnownNat (n+2) constraint in the type signature of the following function: Using the plugin you can omit the KnownNat (n+2) constraint: The plugin can derive KnownNat constraints for types consisting of: Type variables, when there is a corresponding KnownNat constraint Type-level naturals Applications of the arithmetic expression: +,-,*,^ Type functions, when there is either: a matching given KnownNat constraint; or a corresponding KnownNat<N> instance for the type function To use the plugin, add the Pragma to the header of your file.
ghc-typelits-knownnat is a tool in the Build Automation category of a tech stack.
ghc-typelits-knownnat Pros & Cons
Pros of ghc-typelits-knownnat
No pros listed yet.
Cons of ghc-typelits-knownnat
No cons listed yet.
ghc-typelits-knownnat Alternatives & Comparisons
What are some alternatives to ghc-typelits-knownnat?
NuGet
A free and open-source package manager designed for the Microsoft development platform. It is also distributed as a Visual Studio extension.
RubyGems
It is a package manager for the Ruby programming language that provides a standard format for distributing Ruby programs and libraries, a tool designed to easily manage the installation of gems, and a server for distributing them.
Bower
Bower is a package manager for the web. It offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. There are no system wide dependencies, no dependencies are shared between different apps, and the dependency tree is flat.
