You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 679d1e1
Browse filesBrowse the repository at this point in the historyBrowse files
fix(java): a JVM leaf-name fallback never picks a generated accessor
When a JVM LSP callee has no exact node and no Class.method tail match,
cbm_pipeline_lsp_target_node takes the one project callable with that
leaf name. A record accessor became such a callable: on elasticsearch
`Objects.nonNull(x)` (37 CALLS) and `filter(Objects::nonNull)` (230
CALL_REFERENCE) bound a test record's nonNull() accessor.
A generated member is registered by qualified name only. It still joins
through its owner's Class.method tail, but the leaf-name fallback no
longer considers it, either as the unique callable or as a rival that
makes a same-named project callable ambiguous, so every other bind is
decided exactly as before the accessors existed.
The record pipeline fixture gains a record Seen(boolean nonNull) with
`Objects.nonNull(o)` and `filter(Objects::nonNull)` callers. Without the
change it fails in the sequential, parallel and incremental venues.
Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
0 commit comments