They really run into interesting problem here. Should they treat the inode as a string (since it's not likely anyone would do mathematical operation on it), use a two field uint32 array (for correctness) or hash into a 53 bit value (which can't be reversed into the existing windows API). Hard one. +1 for the uint32 array field which I think makes the most sense.
I think you should have error codes ("enums") all the way and the a way to translate these into error messages. That removes a lot of problems with spelling, changing the error message and interoperability with outers using your package.
If you compare (gcc7 and latest clang), how much in pair is gcc with clang in terms of compilation warnings? (One of the most valuable tool of a compiler). I'm really happy they are moving in the same direction; I've been worried about gcc.
I assume it's fairly new since you're posting it (without context)? However isn't it almost expected for a project like this to be on github? (hey, github is the search engine of code)?
I think most of my timeout/deadlines relative to the monotonic time. Hence specifying the absolute monotonic time would just involve yet another syscall (to query the time). Is there a really good argument to specify a absolute monotonic time?
Even if your program is great. You really need to fix the UI, it looks like it was designed when visual basic 6 still were cool. And I could for that reason not take it seriously.
Speaking of Transport Security, last night I got bitten by the removal of OpenSSL headers in Xcode in favor of their own "-framework security" aka Secure Transport.
Is it good or bad if we go down this road? Should SMTP stay ASCII at the expense of the majority of the world? Is there any other protocol which has gone UTF8?
It's nice AWS focuses more in the EU. But how does AWS align with EU data protection laws now and in near future (in the regards of being a American company operating in the EU).