News for hackers. Stuff that matters.
Re:Null Pointer Dereferencing Causes Undefined Behavior by lmm on Monday April 20, 2015 @05:33PM (#9411000)
By not having null pointers. If you want to have a pointer that might not point to anything valid, you do that explicitly with an option type. Of course if you really need to use a possibly-invalid pointer for performance you can drop into unsafe mode.

(At least, the above is what I'd expect from a language like Rust)

Re:Null Pointer Dereferencing Causes Undefined Behavior by yonran on Monday April 20, 2015 @07:15PM (#9411402)
But when you do need unsafe code (e.g. for defining a structure that interacts with a C API), is behavior undefined? I’m just looking at a bit of my own offsetof calculation and hoping it won’t break once I turn optimizations on.

    unsafe extern "stdcall" fn callback(arg0: *const IUnknown) {
        let myself: &MyStruct = &*(arg0.offset(-(&((*std::ptr::null::<MyStruct>()).as_event_handler) as isize)) as *const MyStruct);
    }
Re:Null Pointer Dereferencing Causes Undefined Behavior by dbaupp on Monday April 20, 2015 @08:55PM (#9411740)
Yes, it generally is. Rust has similar (but not the same) undefined behaviours to C/C++, the compiler just ensures that they can't happen in safe code.