These are not easy functions to write good examples for. This might be better suited for a blog post. But if someone has a good idea for how to present these functions in a way that helps people use them correctly and meaningfully, go for it.

These function are essential for doing GUI and graphic programming on many OS, because on many systems, only the first main thread may interact with the GUI or the OS's graphics subsystem.

In general, I feel that Go needs to focus not only on being a back end language but also more on native development. An official go lang blog post on the topic, with descriptions of LockOsThread and UnlockOsThread included would be very welcome indeed, and time permitting, I would certainly like to help proofread or smake suggestions for such a post.

@ianlancetaylor I think a good example is for ensuring execution on the main thread which is often required when integrating with platform specific UI libraries or say WebKit's JavaScriptCore component.

On those situations one would have to "acquire" the main thread early in the application's startup (the main func) and then execute the rest of the code in a goroutine that is not on the main thread.

Actually I think that the example provided in the Wiki is a great one:

• https://github.com/golang/go/wiki/LockOSThread#solutions

Perhaps adding such link to the doc.go of the LockOSThread sources would suffice?

Thank you for raising this reference @triztian that's in the wiki! Good points @beoran about also native development, @eliasnaur presented https://gioui.org at Gophercon 2019 https://www.youtube.com/watch?v=9D6eWP4peYM.

@eliasnaur @hyangah if y'all are free and have bandwidth, might you be interested in an official blog post showing how to use these functions as Ian suggested? Please don't feel obligated to do this, I just figured you are both are domain experts :)