Skip to content

test(java): pin enum constants surviving alongside enum methods #1771

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DeusData merged 1 commit into from
Aug 20, 2026
+9 −0
Merged

test(java): pin enum constants surviving alongside enum methods #1771

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions tests/test_extraction.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -472,6 +472,15 @@ TEST(java_enum_dedup_preserves_calls_issue1234) {
ASSERT(has_def(r, "Enum", "Day"));
ASSERT(has_def(r, "Method", "isWeekend"));
ASSERT(has_def(r, "Method", "label"));
/* The enum CONSTANTS must survive alongside the methods. Reaching the
* methods means descending into enum_body_declarations, and the tempting
* way to do that -- redirecting the shared find_class_body -- also makes
* the constants unreachable, because they are siblings of that node rather
* than children. find_class_member_body exists to descend for members only
* and leave find_class_body (which extract_enum_members uses) alone; these
* two assertions are what stop that distinction being collapsed again. */
ASSERT(has_def(r, "Variable", "MON"));
ASSERT(has_def(r, "Variable", "SUN"));
ASSERT(has_def(r, "Class", "DayUtil"));
ASSERT(has_def(r, "Method", "describe"));
ASSERT_EQ(count_defs_with_label(r, "Function"), 0);
Expand Down
Loading