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 摘要。