If you put (the unix-only) AsRawFd on a trait bound, does that mean that it now can't be compiled on Windows? Or is Rust happy to omit that bound for Windows and continue on, as it can't possibly hold anyway?
-
Show this thread
I know I could work around this by setting #[cfg(unix)] on the type declaration, and just declare it twice (one with AsRawFd in the bound, one without). But the amount of duplication that creates is really not worth it for this case. So I'm curious if there's other ways.
4:17 AM - 26 Mar 2019
0 replies
0 retweets
2 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.