chrysn

Maintaining additional EDHOC backends would add a significant maintenance effort (even beyond the initial porting). If there's a runtime reason, that's fine, but as long as we're just talking of...

I appreciate the enthusiasm, and I'll try to give any PR a better review than is my track record so far, but I still don't quite understand the trade-offs here:...

Two observations that I hope help in the discussion: * GitHub action output can collapse verbose output sections if the right markers are in there. * Even the default output...

Note that c2rust used to compile just fine also on stable Rust. So as theoparis mentioned in the update, unlocking time-rs-macros sounds like the way to go. We need time...

@anjx123: c2rust had that issue too, but has since just moved away from single parentheses in . (I don't know proc macros well enough to have an opinion on whether...

Dropped it in the [RIOT OS matrix chat](https://matrix.to/#/!pqHdpanAvkJvlCwUDE:matrix.org/$NWXLn75xEJ3-dubN3x2mhlKK6XfLqnNqRs3yoGBdyVE?via=matrix.org&via=utwente.io&via=tu-dresden.de)

> This Week In Rust? [Like this?](https://github.com/rust-lang/this-week-in-rust/pull/5852)

Could the `.hdr` pointer stay there unused and deprecated if none of the non-UDP gcoap modules are enabled? Then users who just upgrade their applications would see a deprecation rather...

To clarify: If it's only the Rust wrappers affected, workarounds are possible (but necessary) to make things work there by detecting whether any code getter/setter is present. But if making...

Yes, an unnamed union `.buf ∪ .hdr` that only has the old item if that is legal (ie. UDP is the only transport) would be good. CI should probably not...