Not a feature request, bug report or anything... Just sharing what i've found after doing minimal research + testing
There are 3 OS-dependant functions in the API:
configureTtyNonBlocking: Apparently, Windows is non-blocking by default: This would be a nop, easy
configureSerialNonBlocking: As far as i can tell, you can't change an open file's configuration (well, get current config and reopen with changes, i guess).
Either doing that, or directly opening in non-blocking mode, would require manual low-level fiddling with windows-API calls or PR'ing such options to upstream zig ( FILE_FLAG_OVERLAPPED). I didn't feel like messing that much 😛
restore: Shall be trivial, just undo the overlapped flag if we had to add it
ikskuh
commented
2 months ago
Not a feature request, bug report or anything... Just sharing what i've found after doing minimal research + testing
There are 3 OS-dependant functions in the API:
configureTtyNonBlocking: Apparently, Windows is non-blocking by default: This would be a nop, easyconfigureSerialNonBlocking: As far as i can tell, you can't change an open file's configuration (well, get current config and reopen with changes, i guess).FILE_FLAG_OVERLAPPED). I didn't feel like messing that much 😛restore: Shall be trivial, just undo theoverlappedflag if we had to add it