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

Access to low-level memory mapping #3656

Closed
gopherbot opened this issue May 22, 2012 · 2 comments
Closed

Access to low-level memory mapping #3656

gopherbot opened this issue May 22, 2012 · 2 comments

Comments

@gopherbot
Copy link
Contributor

by raul.san@sent.com:

The use of mmap/mlock could be encapsulated within higher level library (in package
unsafe).

This is really necessary to handle sensitive information like [passwords][1]

[1]: https://groups.google.com/d/msg/golang-nuts/KvgjNbCXTY4/wk8ClfR2YLcJ
@ianlancetaylor
Copy link
Member

Comment 1:

syscall.Mmap and syscall.Mlock already exist.  I don't see why encapsulating them in the
unsafe package would be appropriate.  Why not just write a package that does what you
want?

@rsc
Copy link
Contributor

rsc commented May 22, 2012

Comment 2:

Status changed to WorkingAsIntended.

@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants