mlib VS flipperzero-firmware

This uses the preprocessing library

M*LIB

Thanks to your feedback, I have added a new chapter in the documentation explaining how to do what you want. In this case, you need to inherit from the integer oplist (M_BASIC_OPLIST) and only adds the operator you need using the macro M_OPEXTEND. I have also added examples for integer and for c-string that may help you since there weren't any example with OA hashmap.

A quick bench on array(unsigned) between RXI vec and M*LIB array, which uses type generation, shows 1476 ms for RXI vec and 1116 ms for M*LIB (O2 / native / No LTO).

That was definitely part of the pain: I'm not fluent in C (professionally mainly write golang), so everything was taking me more time, and I was cursing the lack of all the niceties I'm used to. Having access to mlib that came with the firmware did help a lot, but still... Then also having to run everything through the flipper, 'screening' to it to get logs, etc. was just that extra little bit of pain.

Man I got really excited thinking this was about the Flipper Zero device https://flipperzero.one/

We use littlefs in Flipper Zero's firmware[1] for storage in leftover flash space after the main firmware image. Flipper implements a virtual FS, where both external SD card and internal storage have own mount points. SD card is used for storing apps and user-created data, and internal littlefs contains persistent data like BLE pairing, system services configs and such.

We never had any issues with littlefs - however, it cannot be easily repartitioned when amount of available leftover space changes with firmware updates. So on installing an update, it gets fully backed up to SD card, reformatted and later restored.

1- https://github.com/flipperdevices/flipperzero-firmware/blob/...

Issue opened.

It is used in FlipperZero with FreeRTOS to handle the data structure.