doc: go_mem.html is unclear about io as synchronisation mechanism #53334
Labels
Documentation
Issues describing a change to documentation.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
https://tip.golang.org/ref/mem does not speak about os operations.
Is a
syscall
a synchronization primitive if the underlying os says the corresponding syscall is ?In other words:
Legal code ? (assuming posix)
Please ignore the fact that this code is completely unrealistic, this could realistically come up in edge cases of real code.
The text was updated successfully, but these errors were encountered: