Windows process.username optional but POSIX process.uid required?

[wking]

On POSIX (currently Linux and Solaris), uid and gid are required. My preferred approach here is to make those optional and use platform defaults:

If unset, the runtime will not attempt to manipulate the user ID (e.g. not calling setuid(2) or similar).

But the maintainer consensus is that they want those to be explicitly required properties.

The Windows username, on the other hand, is optional, although the default behavior is unclear. I see no discussion in #565 to suggest whether this was intentionally approved or not.

So the current spec seems to have different policies for whether user information is required, and it would be nice to make that consistent. I'd rather make it consistent by making the POSIX fields optional. Is the implicit support for an optional Windows username sufficient grounds to make the POSIX fields optional? Or was the optional username an accident? Or do maintainers approve of the current inconsistency?

[crosbymichael]

No, both should be made explicit unless there is something on windows that prohibits this.

[wking]

Or do maintainers approve of the current inconsistency?

They do.