meta-rust
Update to newer cargo, fix issue #79
This specifies cargo = ">=0.82.0" in Cargo.toml but actually resolves to 0.83.0 in Cargo.lock.
Putting >= in version requirements is usually bad, because it means you are not reducing the range to versions that fall in 0.82.n (what semver defines as ^0.82 or in Rust simply 0.82), but you are allowing any future version to be picked up by the dependency solver. Every once in a while, cargo will make a breaking change to their API that will affect you and break the build. The right thing to do is to pin a version as has always been done, and just bump it when new versions come out.
See https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html for more info.
@TaborKelly thanks, you saved me. cargo-bitbake wasn't working anymore after updating my dependencies and Rust
