Pre release stuff!!!
Pre release stuff!!!
panic: runtime error: nil pointer dereferences can be avoided in #rustlang, but not #golang, and this code dereferenced one at runtime and the code didn't bother to check, and the reviewer didn't catch it either. Use a better language.
TIL that in #javascript, parseInt(0.0000005) results in 5.
Here's the equivalent in rust. Definitely too verbose. play.rust-lang.org?version=stab...
TIL that in #javascript, parseInt(0.0000005) results in 5.
Here's the equivalent in rust. Definitely too verbose. play.rust-lang.org?version=stab...
Why is that? Because off-by-one errors and overflow errors are a major source of bugs. Enable this lint and use checked operations instead of just raw math.
rust-lang.github.io/rust-clippy/...
Why is that? Because off-by-one errors and overflow errors are a major source of bugs. Enable this lint and use checked operations instead of just raw math.
rust-lang.github.io/rust-clippy/...
Here's their rust implementation, rolled out quite quickly.
Here's their rust implementation, rolled out quite quickly.
rewriting in Go is usually just trivial syntactic transformation, while rewriting in Rust often requires rearchitecturing code and thinking about ownership.
generally, GC makes code easier to write at the cost of runtime performance.
"Rust continues to dominate in areas where performance and safety are non-negotiable, albeit with a steeper learning curve.". #rustlang
"Rust continues to dominate in areas where performance and safety are non-negotiable, albeit with a steeper learning curve.". #rustlang