Skip to content

resolve: Java super/type parameters/source roots, self-init calls, Rust test modules - #22

Draft
dangzitou wants to merge 1 commit into
NianJiuZst:mainfrom
dangzitou:fix/java-rust-resolution-precision
Draft

dangzitou wants to merge 1 commit into
NianJiuZst:mainfrom
dangzitou:fix/java-rust-resolution-precision

Conversation

@dangzitou

Copy link
Copy Markdown

Summary

Resolver fixes found by indexing two large Java projects (Apache commons-lang, 631 files; Guava, 3,281 files with a duplicated android/ source tree) and by re-sampling Tokio misses against upstream. Each fix targets a concrete wrong or missing edge class; Express and Gin graphs are unchanged.

Java

  • super.m() keeps its receiver. The kernel names it bare m, so it bound to the caller's own override (fake recursion). The Java facts now restore super.m through the existing call_names path, and the call resolves in the ancestors.
  • Class and method type parameters (<T>) become TypeParam bindings, reusing the existing Rust mechanism. Before, T resolved to any enum constant named T (commons-lang's test enum TooMany { T, E, R, ... } received 1,614 references edges).
  • One FQN in several source roots resolves to the copy nearest the referencing file by directory distance (same-package lookup, imports, and equal-qname global ties). Before, guava-tests and guava linked into android/guava (36k call edges), although guava-tests/pom.xml depends on the root guava module.
  • A supertype clause cannot name the declaring class's own nested type (class CompareToBuilder implements Builder<Integer> with a nested Builder).

All languages

  • let rt = rt(); / copy = self.copy(): a call is not shadowed by the local its own line declares when that local is initialised by a call of the same name; an earlier binding (e.g. a callable parameter in default = default()) still applies. This generalises the existing Swift-only swift_self_init, which is unchanged.
  • In Rust, Java/Kotlin and Go, a name-only (global-name) guess never targets the caller itself, e.g. std.sync_all() inside tokio's File::sync_all. Dynamic languages are excluded because they really recurse through untyped children (Django child.relabel_aliases(...)).

Rust

  • Inline mod support { pub mod panic; } in a test crate root maps to tests/support/panic.rs (35 Tokio integration tests use this).

ENGINE_VERSION 11 → 12.

Results (main faf5dea → this branch)

Same repositories, same upstream oracle (codegraph 1.6.2). Guava targets are folded across android/ (matched on path, kind and qualified name) so the copy choice itself is not scored.

Repository Change
commons-lang references P 78.5% → 94.5% (R unchanged); super.x() self-bound 126 → 0; self-loop calls 205 → 79
Guava (folded) references P 81.9% → 89.2%; calls R 91.1% → 91.7%; guava-tests→android call edges 36,395 → 0; super.x() self-bound 1,154 → 0
Tokio calls R 63.6% → 65.2%, labeled P* 79.7% → 80.1%; 10 self-loop guesses removed
Django +26 call/instantiate edges, all checked by hand (e.g. copy = self.copy(), EndToken = EndToken())
Express, Gin identical edge sets

Validation

  • 397 workspace tests pass (1 existing ignored); 3 new e2e tests, each failing on main.
  • Strict clippy (-D warnings) clean; only the changed files were formatted.
  • Incremental == full rebuild: Tokio bench sync ×100, Django ×50, plus targeted Java edits (a super target gaining an override; deleting and restoring an android/ copy).

Not in this PR / notes for review

  • Main's Java overload selection still picks an overload whose parameter count does not fit the call in 3.0% of Guava method-call edges (0.6% in commons-lang). An earlier arity-only version of this work had Guava at 0.8%; that could be a follow-up on top of call_args.
  • Pre-existing on main, not introduced here: adding a new class T.java to commons-lang leaves the incremental index different from a full rebuild (status of a few ContextedExceptionTest refs). Reproduces identically with main's binary.
  • cgr bench sync has no rename rule for .java, so Java incremental checks were manual.
  • The upstream oracle is often the side that is wrong for Java (it picks wrong overloads in 5.6–8.7% of method calls, and links TypeUtils.toString(x) to a nested class's toString). Agreement numbers above should be read together with the semantic checks, not as ground truth.

🤖 Generated with Claude Code

…st test modules

Java
- `super.m()` keeps its receiver (the kernel names it bare `m`), so it resolves in
  the ancestors instead of binding to the caller's own override.
- Class and method type parameters (`<T>`) become TypeParam bindings, so `T` no
  longer links to an enum constant named `T`.
- One FQN in several source roots (guava/, android/guava/) resolves to the copy
  nearest the referencing file by directory distance: same-package lookup,
  imports and equal-qname global ties.
- A supertype clause cannot name the declaring class's own nested type.

All languages
- `let rt = rt();` / `copy = self.copy()`: a call is not shadowed by the local its
  own line declares (an earlier binding, such as a parameter, still is). Swift's
  existing rule is unchanged.
- In Rust, Java/Kotlin and Go a name-only guess never targets the caller itself
  (`std.sync_all()` inside `File::sync_all`).

Rust
- Inline `mod support { pub mod panic; }` in a test crate root maps to
  tests/support/panic.rs.

ENGINE_VERSION 11 -> 12.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dangzitou

Copy link
Copy Markdown
Author

中文说明与实验证据

这条评论用中文补充说明每个改动修的是什么,并附上真实项目上的原始终端输出(同一份源码分别用 main 和本分支建索引,再用 cgr 自带命令或 cgr export --sqlite 导出的数据库直接查询)。输出内容未经改写;为控制篇幅省略了部分无关行,少数长前缀用 ... 缩写,均在对应位置注明。

实验环境

  • 对比版本:main faf5dea ↔ 本分支 2cdc785,均为 cargo build --release --locked -p cgr
  • 机器:Apple M5,macOS 27.0.1,rustc 1.98.1
  • 真实项目(固定 commit):Apache commons-lang c833cc1(631 个 Java 文件)、Google Guava 7cd44b3(3,281 个 Java 文件,含 android/ 整套副本)、tokio b499257、django a05e16a、express 1c6f1b0、gin 0f09c3a
  • 对照基准:上游 codegraph 1.6.2(@colbymchenry/codegraph)

1. Java super.m() 被连到调用者自己

问题:内核把 super.setUseClassName(x) 记成裸名 setUseClassName,解析时先找到当前类自己的同名方法,于是变成"自己调自己"。commons-lang 里 149 处 super.x() 有 126 处是这样,Guava 是 1,221 处里 1,154 处。

修复:Java facts 层用已有的 call_names 机制把接收者恢复成 super.setUseClassName,交给 call_super 在父类链里找。

原始输出(commons-lang)
$ grep -n "public class StandardToStringStyle\|public void setUseClassName\|super.setUseClassName" src/main/java/org/apache/commons/lang3/builder/StandardToStringStyle.java
36:public class StandardToStringStyle extends ToStringStyle {
525:    public void setUseClassName(final boolean useClassName) {
526:        super.setUseClassName(useClassName);

--- main: cgr callees setUseClassName --file src/main/java/org/apache/commons/lang3/builder/StandardToStringStyle.java
No callees found for "setUseClassName"
--- 本分支
**Callees of setUseClassName (1 found)**

- setUseClassName (method) - src/main/java/org/apache/commons/lang3/builder/ToStringStyle.java:526

# CLI 隐藏了自环,所以 main 显示"没有被调用者";导出的数据库里能看到 main 实际是一条自环边:
$ sqlite3 commons-lang.main.sqlite "<StandardToStringStyle.java:526 的 calls 边>"
org.apache.commons.lang3.builder::StandardToStringStyle::setUseClassName  --calls-->  org.apache.commons.lang3.builder::StandardToStringStyle::setUseClassName   (line 526, resolved_by=receiver-type)
$ sqlite3 commons-lang.br.sqlite "<StandardToStringStyle.java:526 的 calls 边>"
org.apache.commons.lang3.builder::StandardToStringStyle::setUseClassName  --calls-->  org.apache.commons.lang3.builder::ToStringStyle::setUseClassName   (line 526, resolved_by=receiver-type)

# 反过来查父类方法的调用者:main 漏掉了这个子类
--- main: cgr callers setUseClassName --file .../builder/ToStringStyle.java
**Callers of setUseClassName (4 found)**
- <ToStringStyle$anon@58> (class) - src/main/java/org/apache/commons/lang3/AnnotationUtils.java:66
- JsonToStringStyle (method) - src/main/java/org/apache/commons/lang3/builder/ToStringStyle.java:131
- NoClassNameToStringStyle (method) - src/main/java/org/apache/commons/lang3/builder/ToStringStyle.java:380
- SimpleToStringStyle (method) - src/main/java/org/apache/commons/lang3/builder/ToStringStyle.java:478
--- 本分支
**Callers of setUseClassName (5 found)**
- <ToStringStyle$anon@58> (class) - src/main/java/org/apache/commons/lang3/AnnotationUtils.java:66
- setUseClassName (method) - src/main/java/org/apache/commons/lang3/builder/StandardToStringStyle.java:526
- JsonToStringStyle (method) - src/main/java/org/apache/commons/lang3/builder/ToStringStyle.java:131
- NoClassNameToStringStyle (method) - src/main/java/org/apache/commons/lang3/builder/ToStringStyle.java:380
- SimpleToStringStyle (method) - src/main/java/org/apache/commons/lang3/builder/ToStringStyle.java:478

2. Java 泛型参数 <T> 被连到名为 T 的枚举常量

问题:Java facts 不记录类型参数,T、E、R 等会走全局名字匹配。commons-lang 测试里恰好有 enum TooMany { T, E, R, ... },结果生产代码的泛型方法产生了 1,608 条指向这个测试枚举常量的 references 边。

修复:Java 的类/方法类型参数记成已有的 TypeParam 绑定(原本只用于 Rust),resolve_type_ref 已经会在作用域里认它,不需要改解析器。

原始输出(commons-lang)
src/test/java/org/apache/commons/lang3/EnumUtilsTest.java:640:enum TooMany {
src/main/java/org/apache/commons/lang3/ObjectUtils.java:666:    public static <T> T getIfNull(final T object, final Supplier<T> defaultSupplier) {

--- main: 指向 TooMany::<字母> 的 references 边
org.apache.commons.lang3::TooMany::T|732
org.apache.commons.lang3::TooMany::E|222
org.apache.commons.lang3::TooMany::R|148
org.apache.commons.lang3::TooMany::O|104
org.apache.commons.lang3::TooMany::L|88
    total: 1608
    例:org.apache.commons.lang3::ObjectUtils::getIfNull --references--> org.apache.commons.lang3::TooMany::T (line 666)
--- 本分支
    total: 0

3. 同一个全限定名在多个源码根下(Guava 的 guava/ 与 android/guava/)

问题:同包查找、import 绑定、全局同名并列时都取"第一个",而排序上 android/ 在前。结果 guava-tests 的 36,395 条调用边连进了 android/guava。但根 pom.xml 里 guava-tests 依赖的是根目录的 guava 模块,android/ 有自己的一套 guava-tests。

修复:多个同名副本时,按目录树距离选离引用文件最近的那份(同包查找、resolve_jvm 的 import、全局并列且全限定名完全相同时)。只在 JVM 上做全局并列的这一步,因为只有 JVM 的 qualified name 带包名;Rust 等语言同名不代表是同一个声明。

原始输出(Guava)
$ grep -n "<module>" pom.xml android/pom.xml
android/pom.xml:31:    <module>guava</module>
android/pom.xml:33:    <module>guava-testlib</module>
android/pom.xml:34:    <module>guava-tests</module>
pom.xml:31:    <module>guava</module>
pom.xml:33:    <module>guava-gwt</module>
pom.xml:34:    <module>guava-testlib</module>
pom.xml:35:    <module>guava-tests</module>

$ sed -n 17,23p guava-tests/pom.xml
  <dependencies>
    <dependency>
      <groupId>com.google.guava</groupId>
      <artifactId>guava</artifactId>
      <version>${project.version}</version>
      <scope>test</scope>
    </dependency>

--- main: cgr callees testBuilderRetainsState --file guava-tests/test/com/google/common/escape/EscapersTest.java
(第二个定义就是 guava-tests 里的那份)
**com.google.common.escape::EscapersTest::testBuilderRetainsState** (method) — guava-tests/test/com/google/common/escape/EscapersTest.java:52
- escape (method) - android/guava/src/com/google/common/escape/Escaper.java:57, 61, 64
- builder (method) - android/guava/src/com/google/common/escape/Escapers.java:54
- setSafeRange (method) - android/guava/src/com/google/common/escape/Escapers.java:55, 63
- setUnsafeReplacement (method) - android/guava/src/com/google/common/escape/Escapers.java:56
- addEscape (method) - android/guava/src/com/google/common/escape/Escapers.java:59, 60
- build (method) - android/guava/src/com/google/common/escape/Escapers.java:57, 61, 64
--- 本分支
**com.google.common.escape::EscapersTest::testBuilderRetainsState** (method) — guava-tests/test/com/google/common/escape/EscapersTest.java:52
- escape (method) - guava/src/com/google/common/escape/Escaper.java:57, 61, 64
- builder (method) - guava/src/com/google/common/escape/Escapers.java:54
- setSafeRange (method) - guava/src/com/google/common/escape/Escapers.java:55, 63
- setUnsafeReplacement (method) - guava/src/com/google/common/escape/Escapers.java:56
- addEscape (method) - guava/src/com/google/common/escape/Escapers.java:59, 60
- build (method) - guava/src/com/google/common/escape/Escapers.java:57, 61, 64
(android/guava-tests 里那份两边一致,仍然连 android/guava)

全仓统计(calls 边,源文件在 guava-tests/ 下):
                      main     本分支
  → android/...      36395        0
  → guava/...           90    32877

4. implements / extends 子句解析成了类自己的嵌套类型

问题:class CompareToBuilder implements Builder<Integer>,而它内部又声明了 public static class Builder。按 Java 作用域规则,supertype 子句不在类体内,看不到自己的成员类型,这里的 Builder 应该是同包的 builder.Builder 接口。main 把 6 个 *Builder 类全部连成"实现自己的嵌套类",这也会污染继承链和后续的成员查找。

修复:extends/implements 的解析结果如果落在声明类自己内部,就排除掉它的成员,按 import → 同包 → 同文件其他类型重新找。

原始输出(commons-lang)
118:public class CompareToBuilder extends AbstractReflection implements Builder<Integer> {
123:    public static class Builder extends AbstractBuilder<Builder> {
$ ls src/main/java/org/apache/commons/lang3/builder/Builder.java
src/main/java/org/apache/commons/lang3/builder/Builder.java

--- main: 指向名为 Builder 的类型的 implements 边(为便于阅读,`org.apache.commons.lang3.builder` 前缀和路径前缀写成 `...`)
...::CompareToBuilder        --implements-->  ...::CompareToBuilder::Builder        (CompareToBuilder.java:123)
...::DiffBuilder             --implements-->  ...::DiffBuilder::Builder             (DiffBuilder.java:83)
...::EqualsBuilder           --implements-->  ...::EqualsBuilder::Builder           (EqualsBuilder.java:111)
...::HashCodeBuilder         --implements-->  ...::HashCodeBuilder::Builder         (HashCodeBuilder.java:115)
...::ReflectionDiffBuilder   --implements-->  ...::ReflectionDiffBuilder::Builder   (ReflectionDiffBuilder.java:90)
...::ToStringBuilder         --implements-->  ...::ToStringBuilder::Builder         (ToStringBuilder.java:117)
--- 本分支
...::CompareToBuilder        --implements-->  org.apache.commons.lang3.builder::Builder  (src/main/java/org/apache/commons/lang3/builder/Builder.java:75)
...(其余 5 个相同,均指向 builder/Builder.java:75)

5. let rt = rt(); / copy = self.copy():初始化表达式看不到它正在声明的变量

问题:同一行声明的局部变量把同名调用"遮蔽"了,调用被判为 LocalBinding 而不连边。main 已经有只针对 Swift 的 swift_self_init,这里推广到所有语言,但条件更严:只有当该局部变量的初始化表达式本身就是对这个名字的调用时才跳过它,并且会继续找更早的绑定(比如同名参数)。这样 [f() for f in fs] 和 default = default()(default 是参数)都不受影响。Swift 原有规则不变。

原始输出(tokio / django,含反例)
$ grep -n "let rt = rt();\|^fn rt()" tokio/tests/rt_local.rs
11:    let rt = rt();
29:    let rt = rt();
45:    let rt = rt();
--- main: cgr callers rt --file tokio/tests/rt_local.rs
No callers found for "rt"
--- 本分支
**Callers of rt (7 found)**
- test_spawn_local_in_runtime (function) - tokio/tests/rt_local.rs:11
- test_spawn_from_handle (function) - tokio/tests/rt_local.rs:29
- test_spawn_local_on_runtime_object (function) - tokio/tests/rt_local.rs:45
- test_spawn_local_from_guard (function) - tokio/tests/rt_local.rs:61

$ sed -n 196,201p django/db/models/aggregates.py
                filter_sql, filter_params = compiler.compile(self.filter)
            except NotSupportedError:
                # Fallback to a CASE statement on backends that don't support
                # the FILTER clause.
                copy = self.copy()
                copy.filter = None
--- main: aggregates.py:200 的 calls 边
    (无;refs: copy=LocalBinding)
--- 本分支
    Aggregate::as_sql --calls--> Func::copy   (refs: copy=Resolved)

# 反例:参数本身可调用,不能误连到某个全局 default 函数
$ grep -rn 'default = default()' django | head -1
django/core/cache/backends/base.py:234:                default = default()
222:     def get_or_set(self, key, default, timeout=DEFAULT_TIMEOUT, version=None):
--- main:   default=LocalBinding, edges: 0
--- 本分支: default=LocalBinding, edges: 0

6. 静态类型语言里,"按名字猜"的结果不能是调用者自己

问题:接收者类型未知时有个按方法名全局唯一匹配的兜底(global-name)。在 Rust/Java 里接收者常是标准库对象,方法名恰好和项目里的同名,比如 tokio File::sync_all 里的 std.sync_all()(std 是 std::fs::File),被猜成了 tokio 自己的 File::sync_all,形成假递归。

修复:仅对 Rust、Java/Kotlin、Go,global-name 结果等于调用者时丢弃。动态语言保留原样,因为 Django 的 child.relabel_aliases(...) 这类是真实的递归(第一版没有限制语言,在 Django 上发现误删后改成了现在这样)。

原始输出(tokio)
$ sed -n 318,323p tokio/src/fs/file.rs
        let mut inner = self.inner.lock().await;
        inner.complete_inflight().await;

        let std = self.std.clone();
        asyncify(move || std.sync_all()).await
    }
--- main: tokio/src/fs/file.rs 中的 global-name 自环
    File::sync_all --calls--> File::sync_all (line 322, resolved_by=global-name)
    File::sync_data --calls--> File::sync_data (line 357, resolved_by=global-name)
    File::set_len --calls--> File::set_len (line 409, resolved_by=global-name)
    File::set_len --calls--> File::set_len (line 411, resolved_by=global-name)
    File::try_clone --calls--> File::try_clone (line 479, resolved_by=global-name)
    File::set_times --calls--> File::set_times (line 598, resolved_by=global-name)
    (全仓: 10)
--- 本分支
    (全仓: 0)

7. Rust 测试 crate 里的内联模块 mod support { pub mod panic; }

问题:tokio 有 35 个集成测试用这种写法引用 tests/support/*.rs。按 Rust 规则,crate 根里内联模块的外置子模块在根文件所在目录下,但 cgr 把 support::panic 当成外部 crate。

修复:crate 根文件里的相对路径找不到已知模块时,按 <目录>/a/b.rs 或 <目录>/a/b/mod.rs 尝试,只认真实存在的文件。

原始输出(tokio)
$ sed -n 14,17p tokio/tests/sync_panic.rs
mod support {
    pub mod panic;
}
use support::panic::test_panic;
$ ls tokio/tests/support/
io_uring.rs
io_vec.rs
leaked_buffers.rs
mpsc_stream.rs
panic.rs
signal.rs

--- main: cgr callers test_panic --file tokio/tests/support/panic.rs
No callers found for "test_panic"
    (total callers: 0)
--- 本分支
**Callers of test_panic (20 found)**
- read_buf_initialize_unfilled_to_panic_caller (function) - tokio/tests/io_panic.rs:63
- read_buf_advance_panic_caller (function) - tokio/tests/io_panic.rs:78
    (total callers: 63)

整体指标(相对上游 codegraph 1.6.2)

注意:这里的 P/R 是"和上游一致的比例",上游不是标准答案。比如 Java 里上游有 5.6–8.7% 的方法调用选错了重载,Guava 里把 guava-tests 连进 android/。所以上面逐项的语义证据比这张表更能说明对错。Guava 的目标节点按 android/ 折叠后再比(只看路径/种类/全限定名),不让"选哪份副本"本身影响分数。

项目 指标 main 本分支
express 全图 IDENTICAL IDENTICAL
gin 全图 IDENTICAL IDENTICAL
django calls R / 全图 R 76.51% / 90.76% 76.55% / 90.77%
tokio calls R / P* 63.55% / 79.73% 65.17% / 80.10%
commons-lang references P 78.49% 94.49%
commons-lang 全图 P 84.31% 86.25%
Guava(折叠) references P 81.90% 89.15%
Guava(折叠) calls R / 全图 R 91.05% / 94.36% 91.68% / 94.83%
原始输出(compare 脚本 + db_digest)
$ db_digest.py express.main.sqlite express.br.sqlite → IDENTICAL
$ db_digest.py gin.main.sqlite gin.br.sqlite → IDENTICAL

$ compare.py django.main.sqlite django/.codegraph/codegraph.db
kind               cgr      up    both        P        R
calls            48252   54328   41569   86.15%   76.51%
ALL             189560  192833  175014   92.33%   90.76%
$ compare.py django.br.sqlite django/.codegraph/codegraph.db
calls            48277   54328   41586   86.14%   76.55%
ALL             189586  192833  175031   92.32%   90.77%

$ compare.py tokio.main.sqlite tokio/.codegraph/codegraph.db
calls            14786   12729    8089   54.71%   63.55%
ALL              43467   35324   29342   67.50%   83.07%
[calls] P*= 79.73% R= 63.55% labeled=10146 extra-unlabeled=4640
$ compare.py tokio.br.sqlite tokio/.codegraph/codegraph.db
calls            15001   12729    8295   55.30%   65.17%
ALL              43704   35324   29549   67.61%   83.65%
[calls] P*= 80.10% R= 65.17% labeled=10356 extra-unlabeled=4645

$ compare.py commons-lang.main.sqlite commons-lang/.codegraph/codegraph.db
calls            37832   36323   28753   76.00%   79.16%
references        9643    7938    7569   78.49%   95.35%
ALL              73403   69835   61889   84.31%   88.62%
$ compare.py commons-lang.br.sqlite commons-lang/.codegraph/codegraph.db
calls            37811   36323   28751   76.04%   79.15%
references        8010    7938    7569   94.49%   95.35%
ALL              71749   69835   61887   86.25%   88.62%

$ compare.py guava.main.sqlite guava/.codegraph/codegraph.db --fold android/
calls           142722  137150  124876   87.50%   91.05%
references       35743   32719   29272   81.90%   89.46%
ALL             351161  335536  316599   90.16%   94.36%
$ compare.py guava.br.sqlite guava/.codegraph/codegraph.db --fold android/
calls           146578  137150  125740   85.78%   91.68%
references       33366   32719   29745   89.15%   90.91%
ALL             352868  335536  318204   90.18%   94.83%

Guava 的 calls P 下降主要来自新增的 super.x() 父类边和挪回 guava/ 的边,上游没有对应标注,计为"额外边"。

测试与增量一致性

$ cargo test --release --locked -p cg-resolve --test resolve_e2e -- java_overloads java_duplicate rust_inline   # 本分支
test java_overloads_fields_super_and_type_parameters ... ok
test rust_inline_test_modules_self_init_calls_and_guesses ... ok
test java_duplicate_source_roots_resolve_within_their_own_root ... ok
test result: ok. 3 passed; 0 failed; 0 ignored; 0 measured; 59 filtered out; finished in 0.04s
$ (同样 3 个测试放到 main faf5dea 上)
test java_overloads_fields_super_and_type_parameters ... FAILED
test rust_inline_test_modules_self_init_calls_and_guesses ... FAILED
test java_duplicate_source_roots_resolve_within_their_own_root ... FAILED
test result: FAILED. 0 passed; 3 failed; 0 ignored; 0 measured; 59 filtered out; finished in 0.04s

$ cargo test --release --locked --workspace   # 汇总
passed 397 failed 0 ignored 1

$ cgr bench sync tokio --edits 100 --seed 1 --verify --json
{"edits": 100, "deltaSyncs": 82, "fullRebuilds": 18, "incrementalEqualsFull": true}

另外 django 随机编辑 ×50 增量 = 全量;Java 手工改动(让 super 目标多出一个 override、删除再恢复 android/ 下的副本)增量 = 全量。cgr bench sync 目前没有 .java 的改名规则,所以 Java 只能手工验证。

复现方式

# 两个版本分别构建
git checkout faf5dea && cargo build --release --locked -p cgr && cp target/release/cgr /tmp/cgr-main
git checkout fix/java-rust-resolution-precision && cargo build --release --locked -p cgr

# 例:commons-lang
git clone https://github.com/apache/commons-lang && cd commons-lang && git checkout c833cc1
/tmp/cgr-main index . && /tmp/cgr-main callees setUseClassName --file src/main/java/org/apache/commons/lang3/builder/StandardToStringStyle.java
<branch>/target/release/cgr index . && <branch>/target/release/cgr callees setUseClassName --file src/main/java/org/apache/commons/lang3/builder/StandardToStringStyle.java

如果需要,我可以把对比脚本(compare.py 等)整理后放进 scripts/。

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant