Improve documentation for Control.Monad.State
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 52/100
- Tipo di issue
- Documentazione
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Ambito
- documentation
Direzione di ricerca
Find the documentation for State in Control.Monad.State and compare it with the MonadState documentation in Control.Monad.State.Class. Add an explanation of what State means beyond its type alias, including its relationship to MonadState. Done when readers can understand that relationship from the State documentation; the issue names no specific files or tests.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
The documentation for State in Control.Monad.State gives State's type definition as as type StateT s Identity, and says that "The State monad is a synonym for the StateT monad transformer, applied to the Identity monad."
That documentation simply repeats whats' in the type signature, but I have to assume that I'm not alone in finding the type signature opaque. Understanding it requires studying StateT and Identity, and then figuring out what the implications of their combination are.
There's information that seems relevant in the documentation for MonadState in Control.Monad.State.Class, but it's not easy to figure out what the relationship is between MonadState and StateT s Identity. It doesn't seem as if one is normally supposed to use MonadState directly, in any event.
Purescript by Example has some discussion of the State monad. It's helpful, but it's fairly superficial and didn't answer my questions. I didn't find anything helpful for my needs in Jordan's Reference, though it's possible that I haven't looked in the right place. Instead I've been studying Haskell resources to learn about Haskell's Control.Monad.State, which is obviously the model for Purescript's State. However, then one has to worry about possible differences in corner cases or even more substantial semantical features. This becomes a real issue when I translate Haskell code into Purescript and get an error that isn't due to obvious differences between the languages. (e.g. it's obvioius using (x, y) instead of Tuple x y is a mistake). Then it's not clear whether I made a mistake, or whether there's difference in the semantics of the two State monads. Since it's hard to understand the documentation for Purescript's State, figuring out whether there's a difference isn't easy. (The documentation for Haskell's State is confusing, too, but the docs are more detailed, and there are lots of other things one can read about Haskell's State.)
Normally, I'd expect that more explanation of something like the State monad might be found in the package documentation. However, since the Control.Monad.* modules are part of the transformers package, and there are lots of other modules in that package, I can understand why the package documentation doesn't say anything about particular modules or groups of modules.
However, I think there needs to be documentation of State that goes beyond it's type alias definition. One small thing that might help would be a brief explanation within the documentation for State of its relationship to MonadState.
Thanks!
- Lingua principale
- PureScript
- Stelle
- 72
- Fork
- 43
- Merge medio
- 2g 23h
- PR unite (30g)
- 1
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Nessuna guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di purescript/purescript-transformers
-
MonadAsk is over constrainedApertatype: breaking change
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
purescript/purescript-transformers#144 · 2 commenti ·
-
type: documentation
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 28/100
purescript/purescript-transformers#129 · 6 commenti ·
-
type: enhancement
Difficoltà 5/5 Più di una settimana Idoneità per principianti 18/100
purescript/purescript-transformers#123 · 4 commenti ·
-
maybeToExceptTApertatype: enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 42/100
-
type: documentation
Difficoltà 4/5 3-5 giorni Idoneità per principianti 30/100
purescript/purescript-transformers#117 · 6 commenti ·
Tutte le issue di purescript/purescript-transformers
Issue simili
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
kubescape/node-agent#1099 ·
I maintainer di solito rispondono entro 1 giorno
-
[workshop-sim] Improve: Provide a concrete example and activity checks in agentic intro (step 5)Apertafeedback simulation workshop
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
githubnext/gh-aw-workshop#5715 ·
I maintainer di solito rispondono entro 1 giorno
-
documentation type/bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
area-multi-tenancy p1-recommended technical-debt
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
I maintainer di solito rispondono entro 1 giorno
-
Docs: 2 broken linksApertaBug pulumi/pulumi-terraform-bridge R2 S2
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
pulumi/pulumi-terraform-bridge#3713 ·
I maintainer di solito rispondono entro 1 giorno