I'm not sure if this happens from the command-line, but when running the analysis from code one may encounter cases where id.Obj is nil (as documented). This may cause a runtime panic.
I suspect when id.Obj == nil we have nothing to report, which is what this PR does.
Feel free to close if you have another way to resolve.
I'm not sure if this happens from the command-line, but when running the analysis from code one may encounter cases where
id.Obj
is nil (as documented). This may cause a runtime panic.I suspect when
id.Obj == nil
we have nothing to report, which is what this PR does.Feel free to close if you have another way to resolve.