MonadAsk is over constrained

Open
#144 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
backend

Research direction

Read the MonadAsk law and the ask example in the issue, then locate MonadAsk's class definition and law tests in the repository. Check how the constraint permits applicative computations that depend on the environment; done means the constraint and its tests reflect the stated law without requiring effects that depend on the environment.

Written by the indexing model from the issue text.

Description

type: breaking change

The law for MonadAsk ask >>= \_ -> ask = ask only requires Applicative ask *> ask = ask. You can't execute effects depending on the environment, but you can compute results depending on the environment.

example = f <$> ask <*> other
Dominant language
PureScript
Stars
72
Forks
43
Avg merge
2d 23h
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from purescript/purescript-transformers

All issues in purescript/purescript-transformers

Similar issues

More Backend & API Design issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.