pub struct UnixReady(/* private fields */);
Expand description
Unix specific extensions to Ready
Provides additional readiness event kinds that are available on unix platforms. Unix platforms are able to provide readiness events for additional socket events, such as HUP and error.
HUP events occur when the remote end of a socket hangs up. In the TCP case, this occurs when the remote end of a TCP socket shuts down writes.
Error events occur when the socket enters an error state. In this case, the socket will also receive a readable or writable event. Reading or writing to the socket will result in an error.
Conversion traits are implemented between Ready
and UnixReady
. See the
examples.
For high level documentation on polling and readiness, see Poll
.
§Examples
Most of the time, all that is needed is using bit operations
use retty_io::Ready;
use retty_io::unix::UnixReady;
let ready = Ready::readable() | UnixReady::hup();
assert!(ready.is_readable());
assert!(UnixReady::from(ready).is_hup());
Basic conversion between ready types.
use retty_io::Ready;
use retty_io::unix::UnixReady;
// Start with a portable ready
let ready = Ready::readable();
// Convert to a unix ready, adding HUP
let mut unix_ready = UnixReady::from(ready) | UnixReady::hup();
unix_ready.insert(UnixReady::error());
// `unix_ready` maintains readable interest
assert!(unix_ready.is_readable());
assert!(unix_ready.is_hup());
assert!(unix_ready.is_error());
// Convert back to `Ready`
let ready = Ready::from(unix_ready);
// Readable is maintained
assert!(ready.is_readable());
Registering readable and error interest on a socket
use retty_io::{Ready, Poll, PollOpt, Token};
use retty_io::net::TcpStream;
use retty_io::unix::UnixReady;
let addr = "216.58.193.68:80".parse()?;
let socket = TcpStream::connect(&addr)?;
let poll = Poll::new()?;
poll.register(&socket,
Token(0),
Ready::readable() | UnixReady::error(),
PollOpt::edge())?;
Implementations§
Source§impl UnixReady
impl UnixReady
Sourcepub fn error() -> UnixReady
pub fn error() -> UnixReady
Returns a Ready
representing error readiness.
Note that only readable and writable readiness is guaranteed to be
supported on all platforms. This means that error
readiness
should be treated as a hint. For more details, see readiness in the
poll documentation.
See Poll
for more documentation on polling.
§Examples
use retty_io::unix::UnixReady;
let ready = UnixReady::error();
assert!(ready.is_error());
Sourcepub fn hup() -> UnixReady
pub fn hup() -> UnixReady
Returns a Ready
representing HUP readiness.
A HUP (or hang-up) signifies that a stream socket peer closed the connection, or shut down the writing half of the connection.
Note that only readable and writable readiness is guaranteed to be
supported on all platforms. This means that hup
readiness
should be treated as a hint. For more details, see readiness in the
poll documentation. It is also unclear if HUP readiness will remain in 0.7. See
here.
See Poll
for more documentation on polling.
§Examples
use retty_io::unix::UnixReady;
let ready = UnixReady::hup();
assert!(ready.is_hup());
Sourcepub fn is_error(&self) -> bool
pub fn is_error(&self) -> bool
Returns true if the value includes error readiness
Note that only readable and writable readiness is guaranteed to be
supported on all platforms. This means that error
readiness should
be treated as a hint. For more details, see readiness in the poll
documentation.
See Poll
for more documentation on polling.
§Examples
use retty_io::unix::UnixReady;
let ready = UnixReady::error();
assert!(ready.is_error());
Sourcepub fn is_hup(&self) -> bool
pub fn is_hup(&self) -> bool
Returns true if the value includes HUP readiness
A HUP (or hang-up) signifies that a stream socket peer closed the connection, or shut down the writing half of the connection.
Note that only readable and writable readiness is guaranteed to be
supported on all platforms. This means that hup
readiness
should be treated as a hint. For more details, see readiness in the
poll documentation.
See Poll
for more documentation on polling.
§Examples
use retty_io::unix::UnixReady;
let ready = UnixReady::hup();
assert!(ready.is_hup());
Sourcepub fn is_priority(&self) -> bool
pub fn is_priority(&self) -> bool
Methods from Deref<Target = Ready>§
Sourcepub fn is_readable(&self) -> bool
pub fn is_readable(&self) -> bool
Sourcepub fn is_writable(&self) -> bool
pub fn is_writable(&self) -> bool
Sourcepub fn insert<T: Into<Self>>(&mut self, other: T)
pub fn insert<T: Into<Self>>(&mut self, other: T)
Adds all readiness represented by other
into self
.
This is equivalent to *self = *self | other
.
§Examples
use retty_io::Ready;
let mut readiness = Ready::empty();
readiness.insert(Ready::readable());
assert!(readiness.is_readable());
Sourcepub fn remove<T: Into<Self>>(&mut self, other: T)
pub fn remove<T: Into<Self>>(&mut self, other: T)
Removes all options represented by other
from self
.
This is equivalent to *self = *self & !other
.
§Examples
use retty_io::Ready;
let mut readiness = Ready::readable();
readiness.remove(Ready::readable());
assert!(!readiness.is_readable());
Sourcepub fn contains<T: Into<Self>>(&self, other: T) -> bool
pub fn contains<T: Into<Self>>(&self, other: T) -> bool
Returns true if self
is a superset of other
.
other
may represent more than one readiness operations, in which case
the function only returns true if self
contains all readiness
specified in other
.
See Poll
for more documentation on polling.
§Examples
use retty_io::Ready;
let readiness = Ready::readable();
assert!(readiness.contains(Ready::readable()));
assert!(!readiness.contains(Ready::writable()));
use retty_io::Ready;
let readiness = Ready::readable() | Ready::writable();
assert!(readiness.contains(Ready::readable()));
assert!(readiness.contains(Ready::writable()));
use retty_io::Ready;
let readiness = Ready::readable() | Ready::writable();
assert!(!Ready::readable().contains(readiness));
assert!(readiness.contains(readiness));
Sourcepub fn as_usize(&self) -> usize
pub fn as_usize(&self) -> usize
Returns a usize
representation of the Ready
value.
This usize
representation must be treated as opaque. There is no
guaranteed correlation between the returned value and platform defined
constants. Also, there is no guarantee that the usize
representation
will remain constant across patch releases of retty-io.
This function is mainly provided to allow the caller to store a
readiness value in an AtomicUsize
.
§Examples
use retty_io::Ready;
let ready = Ready::readable();
let ready_usize = ready.as_usize();
let ready2 = Ready::from_usize(ready_usize);
assert_eq!(ready, ready2);