Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Java: a static call through a wildcard import resolves to a same-named class in an unimported package

未关闭
#2,976 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
52/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
c, java
领域
tooling

调研方向

Reproduce with the three Java files in the report and CODEGRAPH_KERNEL=0, then trace the qualified-name resolution path for Util.log and compare it with the new Util() path that already applies package/import visibility. The relevant behavior is static-call candidate selection: own package, explicit imports, then on-demand imports. Done means the wildcard case resolves to com.x.b.Util, the explicit-import case still works, and a regression test covers new Util().run().

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

描述

A static call through a Java on-demand (wildcard) import resolves to a same-named class in a package the file doesn't import, while new of the same name in the same file goes to the right one.

// src/com/x/a/Util.java  package com.x.a; public class Util { public static void log(String s) {} public void run() {} }
// src/com/x/b/Util.java  package com.x.b; public class Util { public static void log(String s) {} public void run() {} }
// src/com/x/m/Main.java
package com.x.m;
import com.x.b.*;
public class Main {
    void go() { Util.log("x"); new Util().run(); }
}
call in go edge on main expected
Util.log("x") log in com/x/a/Util.java (qualified-name) ✗ com/x/b/Util.java
new Util() Util in com/x/b/Util.java ✓ same
new Util().run() none run in com/x/b

With an explicit import com.x.b.Util; the static call resolves correctly.

Reproduced on main at 77ee3484 with CODEGRAPH_KERNEL=0. Linux/WSL2, Node 22.23.2.

Expected. The Class.member (qualified-name) path should apply the same visibility the new path already uses: the file's own package, explicit imports, then on-demand imports. A class in a package the file neither is in nor imports is not a candidate.

主要语言
C
星标
73.2k
派生
4.7k
平均合并
3 小时 13 分钟
30 天内合并 PR
579

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

colbymchenry/codegraph 的其他 Issue

查看 colbymchenry/codegraph 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

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