Suppose a value of the following simple state is registered:

# #![allow(unused_variables)]
#fn main() {
#[derive(Interact)]
struct Point {
    x: u32,
    y: u32,
}
#}

The whole of it can be printed, and the result is similar to a pretty printed Debug:

>>> state
Point { x: 3, y: 4 }

Tuple structs are accessed similarly using Rust's .0, .1, etc.

The syntax for field access is similar to Rust's. For example, accessing one of the fields of the previous example:

>>> state.x
3

# #![allow(unused_variables)]
#fn main() {
struct OptPoint {
    x: Option<u32>,
    y: Option<u32>,
}
#}

Suppose that we have an instance of this struct with the following value:

OptPoint { x: None, y: Some(3) }

Unlike in Rust, we can have a full path to the variant's value through variant's name:

>>> state.y.Some
(3)
>>> state.y.Some.0
3
>>> state.x
None
>>> basic.x.None
None

Accessing vectors and maps are done like you'd expected via []. Currently, ranges are not supported in vectors and sorted maps.

Interact elides complexity to access paths when wrapper types are used. For Mutex, it uses .try_lock() behind the scenes. For RefCell it uses try_borrow().