Yea expats are foreign workers that intend to return home after some time. While immigrants are looking to stay.

I still maintain that there is some ambiguity with “US expat” but I ain’t no native speaker. So what do I know.

I don’t understand, will you be an American that temporarily lives and works in another country?

Or will you live and work in America temporarily?

In the latter case: why choose the us?

In the former case: Why only temporarily leave the US?

You probably have a skewed impression. This is common in some places like Germany, but it’s far from the norm. (Even in Germany it’s mostly telecom that does it for some reason.)

Many ISPs only change the allocated IP only in cases like lost connections and some don’t even do that giving out but not guaranteeing static IPs.

No, no, no. It’s the end of times. I can hear the trumpets of the apocalypse.

Now Valve needs to release half life 3 and the world as we know it will truly perish.

Jokes aside. I hope this means work on a UI overhaul can seriously begin.

The only way to make Rust segfault is by performing unsafe operations.

Challange accepted. The following Rust code technically segfaults:

fn stackover(a : i64) -> i64 {
    return stackover(a);
}


fn main() {
    println!("{}", stackover(100));
}

A stack overflow is technically a segmentation violation. At least on linux the program recives the SIGSEGV signal. This compiles and I am no rust dev but this does not use unsafe code, right?

While the compiler shows a warning, the error message the program prints when run is not very helpfull IMHO:

thread 'main' has overflowed its stack
fatal runtime error: stack overflow
[1]    45211 IOT instruction (core dumped)  ../target/debug/rust

Edit: Even the compiler warning can be tricked by making it do recusion in pairs:

fn stackover_a(a : i64) -> i64 {
    return stackover_b(a);
}

fn stackover_b(a : i64) -> i64 {
    return stackover_a(a);
}

fn main() {
    println!("{}", stackover_a(100));
}