armanriazi•rust•unsafe•extern

ArmanRiazi answered on June 5, 2022 Popularity 3/10 Helpfulness 1/10

answer armanriazi•rust•unsafe•extern

related armanriazi•rust•unsafe•static

armanriazi•rust•unsafe•extern

Comment

Functions declared within extern blocks are always unsafe to call from Rust code.
The reason is that other languages don’t enforce Rust’s rules and guarantees, and Rust can’t check them, so responsibility falls on the programmer to ensure safety.
he "C" part defines which application binary interface (ABI) the external function uses: the ABI defines how to call the function at the assembly level. 

extern "C" {
    fn abs(input: i32) -> i32;
}

fn main() {
    unsafe {
        println!("Absolute value of -3 according to C: {}", abs(-3));
    }
}

Popularity 3/10 Helpfulness 1/10 Language rust

Source: github.com

Tags: rust

Link to this answer
Share Copy Link

Contributed on Jun 05 2022

ArmanRiazi

0 Answers Avg Quality 2/10

Closely Related Answers

armanriazi•rust•unsafe•static

Comment

Until now, we’ve not talked about global variables, which Rust does support but can be problematic with Rust’s ownership rules. If two threads are accessing the same mutable global variable, it can cause a data race.
'static lifetime, which means the Rust compiler can figure out the lifetime and we aren’t required to annotate it explicitly. Accessing an immutable static variable is safe.

Popularity 3/10 Helpfulness 1/10 Language rust

Source: github.com

Tags: rust

Link to this answer
Share Copy Link

Contributed on Jun 05 2022

ArmanRiazi

0 Answers Avg Quality 2/10

armanriazi•rust•unsafe•extern

Contents

More Related Answers

armanriazi•rust•unsafe•extern

Closely Related Answers

armanriazi•rust•unsafe•static

Grepper

Documentation

Social

Legal

Contact

Oops, You will need to install Grepper and log-in to perform this action.