joeduffy 6c26693fea Move default to a property on package, not a bit on module ... The old method of specifying a default module for a package was using a bit on the module definition itself. The new method is to specify the module name as part of the package definition itself. The new approach makes more sense for a couple reasons. 1) it doesn't make sense to have more than one "default" for a given package, and yet the old model didn't prevent this; the new one prevents it by construction. 2) The defaultness of a module is really an aspect of the package, not the module, who is generally unaware of the package containing it. The other reason is that I'm auditing the code for nondeterministic map enumerations, and this came up, which simply pushed me over the edge.		2017-02-06 18:33:31 -07:00
..
package.go	Move default to a property on package, not a bit on module	2017-02-06 18:33:31 -07:00
package_url.go	Fix up a bunch of golint errors	2017-01-27 15:42:39 -08:00
package_url_test.go	Clean up package URL logic	2017-01-20 11:46:36 -08:00
stable.go	Reintroduce a handful of binder tests	2017-01-26 16:07:21 -08:00
version.go	Clean up package URL logic	2017-01-20 11:46:36 -08:00
version_test.go	Clean up package URL logic	2017-01-20 11:46:36 -08:00