Go 1.10 Release Notes (DRAFT)
tip.golang.org
tip.golang.org
- LockOSThread/UnlockOSThread now nest.
- LockOSThread + return kills the thread
This is good news for systems programming, as it should allow stuff like ptrace and unshare to behave correctly now! Some context: https://news.ycombinator.com/item?id=14472209
Honest question: Why would somebody ever want to write such an index expression? Is there an actual use case for this, or is it just a hypothetical corner case?
Fossil fell short for me in a few too many ways, but I really liked parts of it. I’m happy to see first-class support for it.
This will make it easier to create a dll and slowly migrate old codebases