@hackage yaya0.6.2.3

Total recursion schemes.

Categories
License
AGPL-3.0-or-later
Maintainer
Greg Pfeil <greg@technomadic.org>
Links
Versions
- 0.6.2.3 Sun, 30 Mar 2025
- 0.6.2.2 Wed, 23 Oct 2024
- 0.6.2.0 Wed, 3 Apr 2024
- 0.6.1.0 Wed, 3 Apr 2024
- 0.6.0.0 Mon, 25 Mar 2024
- 0.5.2.1 Mon, 11 Mar 2024

Installation
Custom
In your cabal file:
Tested Compilers
- 9.10.1
- 9.8.1
- 9.6.3
- 9.6.1
- 9.4.5
- 9.4.1
- 9.2.5
- 9.2.1
- 9.0.2
- 9.0.1
- 8.10.7
- 8.10.1
- 8.8.1
- 8.6.1
Dependencies (11)
- base ^>=4.12.0 || ^>=4.13.0 || ^>=4.14.0 || ^>=4.15.0 || ^>=4.16.0 || ^>=4.17.0 || ^>=4.18.0 || ^>=4.19.0 || ^>=4.20.0
- template-haskell ^>=2.14.0 || ^>=2.15.0 || ^>=2.16.0 || ^>=2.17.0 || ^>=2.18.0 || ^>=2.19.0 || ^>=2.20.0 || ^>=2.21.0 || ^>=2.22.0
- transformers ^>=0.5.5 || ^>=0.6.1
- comonad ^>=5.0.7
- either ^>=5
- free ^>=5.1.5 || ^>=5.2
Dependents (6)
@hackage/yaya-unsafe, @hackage/yaya-quickcheck, @hackage/yaya-unsafe-test, @hackage/yaya-containers, @hackage/yaya-test, @hackage/yaya-hedgehog

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.

Recursion schemes allow you to separate recursion from your business logic – making your own operations simpler, more modular, and less error-prone. This library also provides tools for combining your operations in ways that reduce the number of passes over your data and is designed to encourage total (i.e., successfully terminating) functions.

@hackage yaya0.6.2.3

Categories

License

Maintainer

Links

Versions

InstallationCustom

Tested Compilers

Dependencies (11)

Dependents (6)

Package Flags

Installation
Custom