`definition(String, m)` returns `nothing` for a closure when the enclosing function has arguments
まだ誰も着手していません。
評価
調査の方向性
Start in src/utils.jl at is_func_expr(ex, meth::Method), then run repro.jl with include on the stated Julia and CodeTracking versions to reproduce the parameterized-closure failures. Trace the backward scan, gensym name matching, and argument comparison. Done means definition(String, m) finds the source for all arrow and do-block closures, including those inside functions with parameters.
索引モデルが issue の本文から書いたものです。
説明
definition(String, m) for a closure's method (a do block or a -> inside a call) returns nothing whenever the function it is written inside has parameters. With no parameters it works. The distinction is the enclosing function's argument list, not the closure form or whether the enclosing function is short- or long-form.
Repro (repro.jl, run with include; Julia 1.13.0, CodeTracking 3.0.2, no Revise needed):
using CodeTracking
returnit(f) = f
# short form, enclosing has no args / has args; arrow / do
s_noargs_arrow() = returnit(y -> y + 1)
s_args_arrow(x) = returnit(y -> y + x)
s_noargs_do() = returnit() do y
y + 1
end
s_args_do(x) = returnit() do y
y + x
end
# long form
function l_noargs_arrow()
return returnit(y -> y + 1)
end
function l_args_arrow(x)
return returnit(y -> y + x)
end
function l_noargs_do()
return returnit() do y
y + 1
end
end
function l_args_do(x)
return returnit() do y
y + x
end
end
for (make, args) in ((s_noargs_arrow, ()), (s_args_arrow, (1,)), (s_noargs_do, ()), (s_args_do, (1,)),
(l_noargs_arrow, ()), (l_args_arrow, (1,)), (l_noargs_do, ()), (l_args_do, (1,)))
m = only(methods(make(args...)))
d = CodeTracking.definition(String, m)
println(rpad(string(make), 16), " closure at line ", lpad(m.line, 2), " -> ", d === nothing ? "nothing" : "found (starts at line $(d[2]))")
end
Output:
s_noargs_arrow closure at line 4 -> found (starts at line 4)
s_args_arrow closure at line 5 -> nothing
s_noargs_do closure at line 7 -> found (starts at line 5)
s_args_do closure at line 10 -> nothing
l_noargs_arrow closure at line 14 -> found (starts at line 12)
l_args_arrow closure at line 17 -> nothing
l_noargs_do closure at line 21 -> found (starts at line 18)
l_args_do closure at line 26 -> nothing
Where it happens — is_func_expr(ex, meth::Method) in src/utils.jl:
- The backward scan from the closure's line reaches the enclosing definition, and the name check accepts it on purpose:
fname === strip_gensym(meth.name)maps#l_args_do##0tol_args_do. So far so good — the enclosing definition is the text that contains the closure. - It then "matches the argnames":
exargsare the enclosing definition's parameters (x), zipped againstBase.method_argnames(meth)[2:end], which are the closure's (y).x !== y→return false. When the enclosing function has no parameters the zip is empty and the check passes, which is why thenoargsrows succeed.
So for a gensym-named method the argument check is comparing two different functions' parameter lists. A closure whose parameter names happen to coincide positionally with the enclosing function's would pass by accident.
Suggested fix: when meth.name is a gensym and the expression matched via strip_gensym, skip the argname comparison (the enclosing definition is the right answer, and the caller has meth.line to find the lambda inside it), or locate the ->/do node within ex and compare its parameters instead.
Downstream effect: TypedSyntax calls definition(String, m) first, so Cthulhu's source view cannot show any closure written inside a function with parameters — e.g. stable_hash_helper(x::Tuple, hash_state, context, ::StructTypes.ArrayType) in StableHashTraits, whose do nested_hash_state block reports couldn't retrieve source of (::var"#stable_hash_helper##4#…")(nested_hash_state). Related earlier reports: #102 (added -> matching), #132 (closed; a lambda returned as data, which is a different case — here the file and line are known and correct).
🤖 Filed using Claude Code. The reproduction was run locally on the stated versions and the output is quoted verbatim.
- 主要言語
- Julia
- スター
- 150
- フォーク
- 12
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
JuliaDebug/CodeTracking.jl のほかの issue
-
definition(String, m) returns nothing for anonymous `function (…) … end` closures and for closure keyword-body methods対応中かも @jishnub が 10 日前に担当しました。 オープン
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
JuliaDebug/CodeTracking.jl#163 ·
-
難易度 3/5 1〜2日 初心者へのやさしさ 35/100
JuliaDebug/CodeTracking.jl#143 · コメント 1 件 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
JuliaDebug/CodeTracking.jl#94 · コメント 1 件 ·
-
enhancement help wanted
難易度 3/5 1〜2日 初心者へのやさしさ 45/100
JuliaDebug/CodeTracking.jl#51 · コメント 6 件 ·
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
JuliaDebug/CodeTracking.jl の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
JuliaDebug/Cthulhu.jl#716 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
-
Review dependenciesオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
rafaqz/DimensionalData.jl#1253 ·
-
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
osrep/Runes2P.jl#283 ·
メンテナーはふだん 1 日以内に返信