A deny.toml without an [advisories] section will still check the RustSec when running cargo deny check advisories. This is great and the correct behaviour imo, but it would be good to document the default value for all configuration option and afaict it is not.

Thanks! :)

• Derive serialization for the configuration keys.
• Add the serialized configuration to the fingerprint hash.

We currently only run cargo build, cargo doc and something like cargo fmt --verify on CI. We also need to run the unit tests now that we have them, via cargo test.

• Copy .sdata section from ELF
• Add .sdata and .sbss sections to linker script
• Clear .sbss section in rrt0

So a pattern I've seen a number of places in rust code (and have in my own code in places) is:

impl SomeStruct {
	pub fn new() -> Self {
	    Self::default()
    }
}

In cargo-mutants it will take this function and apply the Default mutagen to it creating code that is equivalent to the source code and then register as not caught. This could be solved by #[mutants::skip]

Currently each PR has the following issue, which should be fixed:

Output of cargo clippy

    Checking cargo-valgrind v2.0.2 (/home/runner/work/cargo-valgrind/cargo-valgrind)
warning: consider adding a `;` to the last statement for consistent formatting
  --> src/panic.rs:76:13
   |
76 |             old_hook(panic)
   |             ^^^^^^^^^^^^^^^ help: add a `;` here: `old_hook(p

As of now the project uses unwrap() methods which may lead to crashes. We should get rid of all of them.