Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

unsafe receive

unsafe { receive } is to receive what unsafe { match } is to match.

Like receive, it scans the mailbox using normal selective-receive rules. Unlike receive, it can match not only BEAM-level primitives such as int(n) and atom(a), but also Patina types based only on their runtime representation.

pub fn main() {
    unsafe {
        receive {
            int(n) => println!("got integer {:?}", n),
            atom(a) => println!("got atom {:?}", a),
            Option::<str>::None => println!("got an empty string option"),
            Option::<int>::None => println!("got an empty integer option"),
            _ => println!("got something else"),
        } after Timeout::from_seconds(5) {
            println!("timeout")
        }
    }
}

unsafe { receive } is unsafe for the same reason unsafe { match } is unsafe: different Patina types can lower to the same BEAM value. The message matched above might have been intended as Option::<str>::None, Option::<int>::None, an ordinary atom, or something else entirely.

It’s best practice to only use unsafe { receive } as a glue, for interop with BEAM libraries and features implemented in other languages.

See also:

unsafe, term, and unsafe { match }