Would this be one last opportunity to make a small number of breaking API changes, or is the idea that users can switch libraries with zero changes besides the import path?

I'd like to make a few small breaking changes before we move go/packages to the standard library. At the least, we're not going to expose LoadFiles/LoadImports/LoadTypes/LoadSyntax/LoadAllSyntax in favor of users explicitly specifying what they need.

(The more opportunities to improve/fix go/packages without actually breaking people the better...)

@matloob where should we file possible breaking changes to the API? Do you want them here or in separate, cross-references issues?

@rsc Before we do this, I think we should have a discussion to make sure that we are okay freezing the API. I'll get in touch with you off line to discuss.

I personally would like some more time to find changes we'd like to make in go/packages before freezing it forever in the standard library, if we plan to do so.

@josharian Separate issues would be best. The cross-referencing should help us track them collectively.