Embedded Working Group Meeting 2022-11-29

Attendance

Write your GH username or Matrix handle here!

Announcements
- smoltcp 0.8.2 released! https://github.com/smoltcp-rs/smoltcp/blob/master/CHANGELOG.md#082–-2022-11-27
Mastodon account
- https://github.com/rust-embedded/wg/issues/647
Critical-section 0.2
- https://github.com/rust-embedded/critical-section/pull/31
- Discussed this point at length
- Yanking 0.2 will break builds for various users with it in their dependency tree,
  especially via atomic-polyfill 0.1 via heapless, or defmt-rtt 0.3
- Releasing 0.2.8 that uses 1.1 internally will fix some use-cases (and not break builds
  that don't actually use the atomics), but will break users that were relying on
  a default impl
- could also release a new atomic-polyfill 0.1.x that depends on c-s 1.1 to help
  force migration e.g. of heapless users, though this also breaks users that depended
  on the default impls
- decided on balance to go with the 0.2.8 release and yank older 0.2.x releases
svd2rust cluster support
- https://github.com/stm32-rs/svdtools/issues/131

Announcements
Is anyone interested in helping run a rust-embedded Mastodon account?
- Yep, https://github.com/rust-embedded/wg/issues/647 opened to track progress
Yank critical-section 0.2?
- Only 4 crates on crates.io still using it exclusively
  - https://crates.io/crates/alkyn
  - https://crates.io/crates/defmt-serial
  - https://crates.io/crates/web-embedded-hal
  - https://crates.io/crates/critical-once-cell
  - rp2040-hal and everything depending on it… https://github.com/rp-rs/rp-hal/blob/main/rp2040-hal/Cargo.toml#L32-L34 – rp2040-hal uses both ~~(in a way that guarantees that nobody accidentally uses the old version)~~ but prevents yanking the old version :)
- Open issue/PR on those 4 crates, wait for rp2040-hal release without it, wait a month and then yank.