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

syscall: should to be migrated to use golang.org/x/sys #14

Open
LionNatsu opened this issue Jan 5, 2017 · 2 comments
Open

syscall: should to be migrated to use golang.org/x/sys #14

LionNatsu opened this issue Jan 5, 2017 · 2 comments

Comments

@LionNatsu
Copy link

Go has deprecated package syscall since 1.4. I think we should use the golang.org/x/sys repository.

See https://golang.org/pkg/syscall/#pkg-overview

@LionNatsu LionNatsu changed the title syscall: should to be migrated to golang.org/x/sys syscall: should to be migrated to use golang.org/x/sys Jan 5, 2017
@songgao
Copy link
Owner

songgao commented Jan 5, 2017

Is there anything in golang.org/x/sys that would benefit this library? syscall is in standard library, thus has backward compatibility guarantees.

I'm not against migrating per se; I guess I'm just not sure about future paths of the two packages.

@LionNatsu
Copy link
Author

@songgao I think the answer is yes. Stability and even compatibility and every bug fix. It has been frozen since 1.4 that means no one line changes since that, but the system interface changes.

A problems list from Go: https://golang.org/s/go1.4-syscall

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants