The rmonad package

[Tags: bsd3, library]

A library for restricted monads based on associated datatypes. This allows datatypes such as Set to be made into monads. Users can either use the NoImplicitPrelude extension and use Control.RMonad directly, or use Control.RMonad.AsMonad with the embed and unEmbed combinators to use the normal Prelude monad operations. The 0.4 release mainly adds support for monad transformers. The dependency on the transformers package may be replaced by mtl if it seems likely that mtl will stay the standard for some time to come.


[Skip to ReadMe]

Properties

Versions0.1, 0.2, 0.3, 0.4, 0.4.1, 0.5, 0.6, 0.7, 0.8, 0.8.0.1, 0.8.0.2
Change logNone available
Dependenciesbase, containers, transformers [details]
LicenseBSD3
Copyright(c) 2008 Ganesh Sittampalam, Peter Gavin
MaintainerGanesh Sittampalam <ganesh@earth.li>
Stabilityprovisional
CategoryControl
UploadedWed Mar 18 22:30:54 UTC 2009 by GaneshSittampalam
DistributionsNixOS:0.8.0.2
Downloads2007 total (108 in last 30 days)
Votes
0 []
StatusDocs not available [build log]
All reported builds failed as of 2015-06-07 [all 2 reports]

Modules

Downloads

Maintainers' corner

For package maintainers and hackage trustees

Readme for rmonad-0.4

rmonad provides a restricted monad class in the Control.RMonad hierarchy.
The class makes use of associated datatypes (available in GHC 6.8),
using an idea learnt from Wolfgang Jeltsch:
http://www.haskell.org/pipermail/haskell-cafe/2008-March/041084.html

It also provides a way to treat a restricted monad as a normal monad
using a generic wrapper type. This idea is described here:
http://hsenag.livejournal.com/11803.html?nc=5

See the haddock documentation for information on how to use it.

darcs get http://code.haskell.org/rmonad

TODO

Add instances for all the mtl stuff. Consider also doing this for mtl-tf
(namespacing issues?)

Add all the normal monad combinators

Should we use Monad etc rather than RMonad etc for naming?
 - Pro: standard modern namespacing conventions
 - Anti: Module names need to be different to allow co-existence

Do we actually want RApplicative etc? Nasty because most restrictions aren't much use on function types
DSELs are a good example of where Suitable could be closed over function types