40: v0.3.3 r=adamgreig a=japaric
changes required to publish a new version
r? @adamgreig (chosen at random)
Co-authored-by: Jorge Aparicio <jorge@japaric.io>
27: Clarify purpose of rerun-if-changed in build.rs r=japaric a=adamgreig
The current `build.rs` contains
```rust
println!("cargo:rerun-if-changed=build.rs");
println!("cargo:rerun-if-changed=memory.x");
```
This causes the build script to be re-run if (and *only if*) `build.rs` or `memory.x` change. The line for `build.rs` is redundant: the Cargo guide [says](https://doc.rust-lang.org/cargo/reference/build-scripts.html#outputs-of-the-build-script) the build script is always rerun when `build.rs` changes, so we can drop that line.
The remaining line caused me a bit of confusion when adding other functionality to my project's build script, before I realised it tells Cargo to *only* rerun the build script when `memory.x` changes, as opposed to the default behaviour which is to rerun it on every build. The comment helps clarify the point of this line, so if users add other functionality to their build scripts it is hopefully easier to notice.
Co-authored-by: Adam Greig <adam@adamgreig.com>
33: Update panic-semihosting dependency to 0.3.0 r=japaric a=plaes
This is due to #[lang = "panic_fmt"] -> #[panic_implementation] breakage
Co-authored-by: Priit Laes <plaes@plaes.org>
