Open ArcaneNibble opened 7 years ago
Arguably the most correct type to accept is a std::ffi::Cstr
, which doesn't have Windows-induced recalcitrance around yielding bytes and which should enforce the no-internal-NULs invariant that I believe is present here.
It is possible to create network device names that are invalid UTF-8 that this crate will not be able to refer to.