Guillaume E

With #1714 merged, we've reached a big milestone in terms of reproducibility. I now have the same hashes when building from master on various folders on the same machine, as...

> Unless we rebase every branch before pulling, it is quite possible/likely that the travis merge commit will introduce meaningful code changes compared to the candidate branch. That's a good...

> Stepping back a bit, I think we should ask what we would like the reproducibility mechanism to look like (this became very stream-of-conscious, but hopefully useful for discussion): >...

While working on https://github.com/google/OpenSK/pull/94, I noticed that although builds seem reproducible across Linux machines (my local development machine vs. GitHub workflows), the binaries obtained on MacOS are currently not the...

I added a reference to https://github.com/tock/elf2tab/pull/16 to track reproducibility of `elf2tab` packaging.

Thanks @jrvanwhy for the proposal. This sounds interesting! Another question would be how to prototype with this to see the performance, code size and memory implications. Maybe my example of...

This could also be gated by one (or several) feature(s). `cfg_attr` can be used to conditionally derive Debug: ```rust #[cfg_attr(feature = "derive_debug", derive(Debug))] struct Foo { ... } ``` And...

I just found out that we are not the only ones wanting a more lightweight formatting in Rust: https://twitter.com/japaric_io/status/1196203591737991168 There is now the `ufmt` crate, streamlining a lightweight `Debug`-like trait:...

Replying here as I think it makes more sense in a separate issue than in a sub-thread of a specific pull-request. > So, what would you propose as a practical...

Thanks for pointing out https://github.com/tock/libtock-rs/pull/20, that's really helpful!