fix the logic of determining the import path vs package name

[mtoader]

a package can be named xxx but it can be located into an archive path/to/xxy

[dlsniper]

Not sure we need this open. The packages seem to work properly and without a proper example I have no clue how to investigate / fix this.

[mtoader]

I want to keep this because there are some subtleties when doing reference resolving that would benefit from this. Also solving this is kind of required for renaming support.

[jamesharr]

Example: https://gist.github.com/jamesharr/8251159

A file defining "package x" doesn't necessarily need to be located in a directory called "x" (as shown in the example). The only restriction Go places on a package is that all the "package x" declarations need to be identical for all "_.go" files in a directory (excluding "__test.go" and probably some others).

As such, you can't rely on the path of the package to determine its name.

[mtoader]

Yep.

[dlsniper]

This one is fixed in 0.9.16-alpha5 (with a follow up in #1087)