• 1 Post
  • 79 Comments
Joined 1 year ago
cake
Cake day: May 10th, 2024

help-circle





  • To me that sounds quite sad. Non sexual nudity is a unique experience it’s unfortunate that many will never be able to enjoy it or disassociate it from sexuality.

    In Germany there are big and accepted nudist spaces. It was also quite the cool experience meeting strangers in a public sauna in Finland. It was such a peaceful environment, as everyone was literally exposing themselves and showing a certain vulnerability that we do not encounter otherwise.












  • 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));
    }