Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's more that by removing the use of unsafe it will play more nicely with the new concurrent garbage collector (slated for Go 1.5 in June).


Thanks for the heads up.

Are also there plans to expose more primitives in unsafe?

I remember seeing some posts related to possible required features as part of re-writing the whole stack in Go.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: