Generalize `filterM` (etc.?) to `Applicative`

未关闭
#162 3 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
42/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
领域
backend

调研方向

Start by reviewing the filterM implementation and the closed pull request #35, which also considered replicateM. Check whether the proposed generalization to Applicative fits the current library API, then identify any related changes from that pull request worth splitting out. Done means a focused change with tests showing filterM works with an Applicative that is not a Monad.

由索引模型根据 Issue 内容生成。

描述

type: enhancement

Today I noticed that PureScript filterM is constrained to Monad, whereas Haskell filterM is constrained to Applicative. After looking at the source code for each and asking on FP Slack, it seems there is no particular reason filterM cannot be more general in PS.

#35 was set to change this and some other things (e.g. replicateM). However, that PR was closed due to staleness. The author @DavidHarrison was going to split it up into individual PRs, but hasn't gotten around to it yet. It seems worthwhile to double-check that PR to see if there is anything else from it you may want to merge.

主要语言
PureScript
星标
61
派生
50
平均合并
2 天 6 小时
30 天内合并 PR
1

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

purescript/purescript-lists 的其他 Issue

查看 purescript/purescript-lists 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。