Imagine a version of Rust in which instead of inserting drop calls, it was an error not to call `.drop()` on any type that implemented `Drop` when it went out of scope. Imagine we decided to change to the semantics we have now - "implicit drop is ruining Rust!!
-
-
My favorite of these is ‘None =>’ will ruin Rust
-
Wait what? How so?! What was it before?


- 1 more reply
New conversation -
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.