@hackage no-recursion0.1.0.0

A GHC plugin to remove support for recursion

Categories
License
AGPL-3.0-or-later
Maintainer
Greg Pfeil <greg@technomadic.org>
Links
Versions
- 0.3.0.0 Fri, 14 Nov 2025
- 0.2.0.0 Thu, 30 Oct 2025
- 0.1.2.3 Sun, 30 Mar 2025
- 0.1.2.2 Mon, 28 Oct 2024
- 0.1.2.0 Sun, 19 May 2024
- 0.1.1.0 Tue, 16 Apr 2024

Installation
Custom
In your cabal file:
Tested Compilers
- 9.8.1
- 9.6.2
- 9.6.1
- 9.4.8
- 9.4.1
- 9.2.8
- 9.2.1
- 9.0.2
- 9.0.1
- 8.10.7
- 8.10.1
- 8.8.4
- 8.8.1
- 8.6.1
- 8.4.1
- 8.2.2
- 8.0.2
Dependencies (2)
- base ^>=4.9.1 || ^>=4.10.1 || ^>=4.11.0 || ^>=4.12.0 || ^>=4.13.0 || ^>=4.14.0 || ^>=4.15.0 || ^>=4.16.0 || ^>=4.17.0 || ^>=4.18.0 || ^>=4.19.0
- ghc ^>=8.0.2 || ^>=8.2.2 || ^>=8.4.1 || ^>=8.6.1 || ^>=8.8.1 || ^>=8.10.1 || ^>=9.0.1 || ^>=9.2.1 || ^>=9.4.1 || ^>=9.6.1 || ^>=9.8.1
Dependents (4)
@hackage/duoids-hedgehog, @hackage/algebraic-graph-duoids, @hackage/duoidal-transformers, @hackage/duoids

Package Flags

noisy-deprecations

(on by default)

Prior to GHC 9.10, the DEPRECATED pragma can’t distinguish between terms and types. Consenquently, you can get spurious warnings when there’s a name collision and the name in the other namespace is deprecated. Or you can choose to not get those warnings, at the risk of not being warned when there’s a name collision and the namespace you’re referencing is the one that’s deprecated.

General recursion can be the cause of a lot of problems. This removes recursion from GHC, allowing you to guarantee you’re using other mechanisms, like recursion schemes.

@hackage no-recursion0.1.0.0

Categories

License

Maintainer

Links

Versions

InstallationCustom

Tested Compilers

Dependencies (2)

Dependents (4)

Package Flags

Installation
Custom