Embedded WG meeting, January 22

[japaric]

8-9 PM CET (Berlin time) on #rust-embedded on irc.mozilla.org

Public Google calendar that includes these weekly meetings

Agenda.

• Prioritize Rust requests Prioritise 2019 wishlist items for rust-lang #269

• @jamesmunns Help with the newsletter

• @jamesmunns Free form discussions? -- Embedded WG meeting, January 15 #291 (comment)

• @korken89 Infinite backtrace, odd backtrace behavior and "corrupted stack?" in GDB cortex-m-rt#139

• @HarkonenBade Adds Shared<T> a wrapper for sharing data between handlers bare-metal#15

• Issues nominated for discussion, if any

• [your topic goes here]

This meeting is open for anyone to attend. If you'd like to bring up any issue / topic related to embedded Rust leave a comment in this issue so we can add it to the agenda.

[japaric]

Prioritize Rust requests #269

We discussed this during the last meeting and so far we have prioritized 10 of the top 15 requests as follows:

1. const generics / Fix Generic associated consts can't currently be used to parameterize fixed array lengths rust-lang/rust#42863 - "Generic associated consts can't currently be used to parameterize fixed array lengths"
2. Stabilize const fn-s that have trait bounds, e.g. const fn new() -> Mutex where T: Send.
3. Stabilize core::mem::MaybeUninit
4. std::io in libcore/liballoc
5. fix Features of dependencies are enabled if they're enabled in build-dependencies; breaks no_std libs rust-lang/cargo#5730 - "Features of dependencies are enabled if they're enabled in build-dependencies; breaks no_std libs"
6. std-aware Cargo / Xargo in Cargo (58 votes) - [Request for Experiment] Sysroot building functionality rust-lang/cargo#4959
7. Improve crates.io or create separate site for no_std crates
8. Support for AVR
9. Stabilize async/await (and all needed underlying machinery)
10. math support in core

These requests still have to be inserted into the above priority list:

• Stabilize RFC 2282 - "Cargo profile dependencies" AKA profile-overrides
• Fix so infinite loops (loop {}) does not need an atomic compiler fence to not be optimized into an abort instruction
• ability to assert within a const fn context, with a compilation error if the assertion fails at compile time and a panic if the assertion fails at runtime.
• Language support for types with storage size of less than 1 byte
• Thumb intrinsics

---

If you think we should increase the priority of any of the sorted items you can make your case at the beginning of the next meeting (2019-01-22). If you can't make it to the meeting then you can leave a comment here and we'll consider it during the meeting.

[korken89]

FYI, I might not be able to make the meeting tonight, sorry for the inconvenience

[japaric]

This meeting happened! Minutes and logs can be found in PR #299.

The agenda for the next meeting is at #300.

@korken89 no problem!