Björn Quentin
Björn Quentin
> @bjoernQ In my previous PR I fixed a HIL test issue by Insuring that the test dropped the `Mem2Mem` struct and in the drop explicitly reset the "memory to...
> This is certainly better than before, but I'm hoping we can get rid of the huge amount of `malloc`s eventually. my thinking was that at least for the things...
I'm not sure if I should change `Vec` into `VecDequeue` for the queues (i.e. FIFO vs LIFO)
Back to draft after observing this: https://github.com/esp-rs/esp-hal/issues/2274#issuecomment-2446807173
False alarm caused by unintendedly enabling ps-max-modem
Microcontrollers like ESP32-C2, ESP32-C3 and ESP32-S2 (other members of the ESP32-family come with support for atomics)
Yes, my initial idea was (2)
> If we take the 2nd approach, is there a way to prevent regression in our CI matrix? How do other no-std projects handle that? Presently our no-std testing is...
> I worry that making trait bounds optional depending on targets will be a pretty big pain in the ass? Yes - I didn't even dare to think about that...
> I do really like idea 2 as well, and would love to see both ideas as options. My initial attempt for idea 2 was unfortunately blocked by this: [taiki-e/portable-atomic#143](https://github.com/taiki-e/portable-atomic/issues/143)...