Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

go/types: don't treat importing of "unsafe" different from other imports #13882

griesemer opened this issue Jan 8, 2016 · 2 comments


Copy link

With the change (per issue #13703), package unsafe is now not special anymore and can be installed and imported like any other package.

Only if it is not found elsewhere is the compiler-known package "unsafe" used.

Make the necessary changes to go/types.

(x/tools/go/types always handled unsafe like other packages - the change is only needed for std lib go/types which handles unsafe directly w/o calling the importer to simplify the importer).

@griesemer griesemer self-assigned this Jan 8, 2016
@griesemer griesemer added this to the Go1.6 milestone Jan 8, 2016
Copy link
Contributor Author

cc @alandonovan

Copy link

CL mentions this issue.

@golang golang locked and limited conversation to collaborators Jan 13, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet

No branches or pull requests

2 participants