(This is used to argue, for example, that Rust isn’t giving you any safety for embedded devices and you might as well write in C.)
-
-
Show this thread
-
Simple example of how the borrow check is important: let mut x: Result<i32,f32> = Ok(1); let y: &i32 = http://x.as _ref().unwrap(); x = Err(1.0); println!(“{}”, y); // unsafe cast of int to float in safe code
Show this thread
End of conversation
New conversation -
-
-
I guess it's nice that the post-INHTWAMA borrow checker is intuitive enough that people think they know what it is without knowing anything about region types.
-
Why did you have to remind me that that acronym exists
End of conversation
New conversation -
-
-
I keep see people repeat again and again that the borrow checker is equal to C++ smart pointers or that it has some sort of runtime cost.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Whenever you tweet something like that I rush to the orange website to look for another Rust-themed brawl.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.