3 ms·
For someone new to Rust. What past changes in the language broke the dependencies you used? Were they using the nightly branch?
by csdreamer7 6y ago
For someone new to Rust. What past changes in the language broke the dependencies you used? Were they using the nightly branch?
- est31 6y agoI ran into two issues, one in rustc-serialize broken by https://github.com/rust-lang/rust/issues/35203 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 :).
- edflsafoiewq 6y agoe: 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)
- steveklabnik 6y agoDoesn't cargo's behavior of capping lints prevent this?
- edflsafoiewq 6y agoYes, you're right. I thought I had seen this in dependencies, but I must have been compiling something directly.