The total information, and general information density in srfi-170.html
suggests that this would better be handled in an another NOTES.[whatever]
file under the srfi subdirectory.  Especially if it's going to be
subject to change in the long term as Windows is not standardized like
POSIX (and per various '00s accounts had lost its backwards compatibility
religion that had famously per Raymon Chen accommodated a use after free
bug for a particular version of SimCity).

And/or have one of the sample implementations work for Windows.

- Harold

----- Original message -----
From: Lassi Kortela <xxxxxx@lassi.io>
Date: Friday, July 31, 2020 5:35 AM

SRFI 170 says which POSIX C function corresponds to each Scheme
procedure. What do you think about listing the closest Windows API
functions as well? The motivation would be to be useful to implementors
and to validate the design so that we chose primivites which are
reasonable to implement on Windows as well (without using Windows
Services for Linux or Cygwin/Msys, which can use the POSIX C APIs and
are great to have, but are not native -- non-native apps always look and
behave a bit differently on each OS which leads laypeople to usually
prefer native apps).