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
gopherbot
added
Tools
This label describes issues relating to any tools in the x/tools repository.
gopls
Issues related to the Go language server, gopls.
labels
Jun 14, 2023
I think the root cause is the behavior of the objectpath package. Given a syntax package containing an unexported type with an exported method, objectpath.For(obj) will succeed and return a path, even if the unexported type is not reachable from any exported declaration. The resulting path will cause objectpath.Object(path, pkg) to fail if pkg was loaded from export data. I'm not sure whether that's that a bug or a feature.
I'm not sure whether that's that a bug or a feature.
I think that's a bug. IMO objectpath.Object should work for any non-empty path returned by objectpath.For. Can we "fix" this by failing objectpath.For in these cases?
I found this while snooping around in 'gopls stats'. This is v0.12.0.
The text was updated successfully, but these errors were encountered: