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
Describe the bug
Several small correctness gaps, each rare, found by the reviews of PR #16:
type I2 I1 (a defined type over an interface) gets kind: interface but no methods or base types; its method set is not populated from the underlying interface.
Panic detection misses a method value taken through a struct that embeds an interface (s.M where s embeds a nil interface), so no exception edge is added.
A method value on a receiver whose type failed to type-check is recorded as a field path (req.Set) in ddgvar. Cosmetic.
Calls on builtin-scope types, such as err.Error(), get a junk internal callee signature (.error.Error). The emitted callee is correctly null, but the internal value is wrong.
Library detection compares paths with filepath.Abs but not EvalSymlinks, so a symlinked project directory can misclassify files.
To Reproduce
Each item names its construct. Fixtures for 1–4 fit in testdata/dataflow.
Expected behavior
Methods and base types populated.
An exception edge.
A method use, not a field.
No signature recorded.
Symlinks resolved before comparing.
Logs
Not applicable.
Additional context
Low priority; grouped to avoid five tiny issues. Split any that grows.
Activity
sinha108 commentedon Oct 25, 2026
Consolidated into #28, which carries this issue's full detail.