IntersectMBO/plutus

`dischargeCekValue` doesn't handle open terms correctly

Open

#7,526 建立於 2026年1月15日

在 GitHub 查看
 (5 留言) (1 反應) (1 負責人)Haskell (1,637 star) (511 fork)batch import
Good first issuebugstatus: triaged

描述

dischargeCekValue has the following code:

                  -- var is free, leave it alone
                  (Var () named)

which means that

(\0 \0 var 2) (delay (var 1))

evaluates to

[1 :-> delay (var 1)] (\0 var 2)

which then discharges to

\0 delay (var 1)

which is variable capture.

貢獻者指南

技術棧
無
領域
backend
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
blocked
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
basic Haskelllambda calculus
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
The bug is in the `dischargeCekValue` function within the Plutus codebase. Start by locating this function, likely in a file related to the CEK machine evaluator. The issue describes variable capture when handling free variables. Review the specific case for `Var () named` and understand how the substitution is performed. Check if there are any existing tests for this behavior. The current assignee may have additional context; consider reviewing any comments for further guidance.