Julien Cretin

Yes, and that would work well with a release branch process. The cron job would check the last commit of all release branches. If a release is not reproducible (for...

To clarify the confusion and situation: - After #156, the ctap2 crate (the one at the root of the git repository) contains both a library and a binary that share...

FYI: If we are afraid of mistakenly using `Result::unwrap` which requires `Debug`, we could enable the [unwrap_in_result](https://rust-lang.github.io/rust-clippy/master/#unwrap_in_result) clippy lint.

> I remember an issue in Tock where this actually had impact on the produced binary (perf + size). But maybe this has either been fixed in the toolchain or...

Or alternatively (or in addition) a workflow to print the binary size diff as a message in PR discussions.

FYI for those looking for a stable crate for base64, base32, hexadecimal, and other standard or custom data encodings: The [data-encoding](https://crates.io/crates/data-encoding) crate has been stable and correct since its first...

> It looks like this can be closed..? Looks like it, but the website would need to be updated to document the new feature. In particular [this](https://github.com/tamasfe/taplo/blob/master/site/site/configuration/formatter-options.md) file should mention...

Same issue with `nRF52840_xxAA` on 0.22.0, so it might not be `RP2040` specific, but it seems indeed specific to 0.22.0. I don't have the problem with 0.21.1 on `nRF52840_xxAA`.

I can reproduce this with the `syn` crate. I suspect `cargo upgrade` is unable to properly read the crates.io index in some circumstances that I couldn't identify. I created #892...

This looks like a dup of #509. Maybe the LSP server should ignore the LSP arguments if there is a taplo.toml? I wonder what rustfmt behavior is, but can't test...