Re:Rust 1.43
by csdreamer7 on Thursday April 23, 2020 @02:29PM
(#22959271)
For someone new to Rust. What past changes in the language broke the dependencies you used? Were they using the nightly branch?
[ Parent
| on HN ]
I ran into two issues, one in rustc-serialize broken by https://github.com/rust-lang/rust/issues/35203 (fixable by cargo update -p rustc-serialize) and one in url broken by the move to NLL on the 2015 edition. The second is an important bugfix in the language, but it still broke my build :). Not sure how I fixed it but it's now fixed as well. Additional changes were required due to openssl.
My own code has compiled just fine except for a ton of warnings (most about try! -> ? change) and the needed API updates of dependencies (2 changed lines).
Most of the effort I spent on actually updating as little as possible. If you update everything you fix all issues resolvable by updates but you also have to adjust to every API change :).
Re:Rust 1.43
by edflsafoiewq on Thursday April 23, 2020 @04:04PM
(#22960543)
e: this is wrong
Dependencies can set lints to deny. When lints change, they might not compile anymore.
(I think denying lints is a bad idea, just like -Werror)
Re:Rust 1.43
by steveklabnik on Thursday April 23, 2020 @04:05PM
(#22960553)
Doesn't cargo's behavior of capping lints prevent this?
Re:Rust 1.43
by edflsafoiewq on Thursday April 23, 2020 @04:24PM
(#22960825)
Yes, you're right. I thought I had seen this in dependencies, but I must have been compiling something directly.