Better error messages for failed subeffect constraints
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- compilers
调研方向
Start by reading the effect constraint generation, effect-provenance graph, and lax-equation unification paths described in the issue; the payload does not name specific files or tests. Trace how subeffect constraints from lambdas, local definitions, casts, and holes are represented, then check how a failed constraint reaches the diagnostic. Done means the error identifies the actual and expected effects and traces failed lax equations back to their originating subeffect constraint.
由索引模型根据 Issue 内容生成。
描述
A subeffect constraint s ⊑ t (the body's effect is a subset of the lambda's effect) has no provenance of its own. When it cannot be solved, it is reported as if it were the equality t ~ s, using the provenance and the MismatchedEffects error of an equality. When the effect-provenance graph finds no path, the leftover lax equation s ∩ ¬t ~ ∅ names neither side, so the message gets worse still.
With subeffecting on by default (#13579), every lambda and local def, checked effect cast and hole produces such a constraint, so these messages will become common.
Proposal:
- Give subeffect constraints a provenance of their own, e.g.
ExpectSubEff(expected, actual, loc), and have the effect-provenance graph treat it as a flow edge through the lambda's effect variable. - Report a failed subeffect constraint with a dedicated error that names the effects of the actual effect that the expected effect does not allow.
- When effect unification fails on the lax equation, trace it back to the subeffect constraint it came from instead of reporting the raw set equation.
#13566 is a first attempt; it is closed in favour of this issue.
🤖 Generated with Claude Code
- 主要语言
- Flix
- 星标
- 2.7k
- 派生
- 194
- 平均合并
- 7 小时
- 30 天内合并 PR
- 137
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
flix/flix 的其他 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 72/100
flix/flix#9715 · 2 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
Effect lock: three package changes that eff-check does not see可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭bug
难度 5/5 一周以上 新手友好度 38/100
维护者通常 1 天内回复
-
A: codegen
难度 4/5 3-5 天 新手友好度 28/100
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 55/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 80/100
objectionary/eo#9762 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
JS/TS: JSX props compile errors should link to a doc page explaining the static-list requirement未关闭area: js-runtime enhancement exists-upstream interop priority: low
难度 2/5 1-3 小时 新手友好度 78/100
shayanhabibi/fickl#307 ·
维护者通常 1 天内回复
-
bug_feature_triaged Team: Mojo Libraries
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 4 天内回复
-
bug fmt low priority
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复