syscall: package is underdocumented

[gopherbot]

by [email protected]:

The standard library syscall package is underdocumented. I was trying to figure how to
write my own utimensat (unimplemented) and I was having a very hard time. What is more,
reading the source of the package doesn't really help, as its code is supposed to be
going through mksyscall.

What I would like to see:

1. An example of writing an unimplemented syscall.

2. How to pass arguments to syscalls (eg. strings should be pointers to nul terminated
byte sequences.

3. Information how to get the right uintptr (reflect or unsafe, when to use each of
them).

4. Documentation any types introduced.

5. A little bit of background information about syscalls would be nice, but that's not
strictly necessary.

[robpike]

Comment 1:

Labels changed: added priority-someday, go1.1maybe, documentation, removed priority-triage, go1.1.

Status changed to Accepted.

[robpike]

Comment 3:

Labels changed: removed go1.1maybe.

[rsc]

Comment 4:

Labels changed: added repo-main.

[rsc]

Comment 5:

Adding Release=None to all Priority=Someday bugs.

Labels changed: added release-none.

[gopherbot]

Change https://golang.org/cl/242999 mentions this issue: syscall: document Sysinfo_t

[seankhliao]

Further work should probably be in x/sys/unix