Nicolas Stalder

I opened to https://github.com/nickray/littlefs2/issues/7 re. ReadDir. I think/hope this issue can be closed in favor of the former, pending merge of https://github.com/nickray/littlefs2/pull/6.

Same comment as for https://github.com/nickray/littlefs2/issues/3: - user can no longer safely construct a File - the `..._and_then` API should fix the UB raised

I have no idea unfortunately - zero experience with this platform.

Awesome. I just put it out as alpha to gather some feedback on the API, do you have any? My main concern is passing in `&mut` constantly, which would be...

Thank you for the feedback, this is helpful! I'm currently using these bindings and getting actual experience myself. > `Filesystem::mount` imposes a lifetime requirement on the `&mut alloc` which means...

> * Many of the APIs seem backwards? `Filesystem::create(...)` would be much clearer than `File::create(&mut Filesystem...)` (and could have the correct associated types from the Filesystem instance) Regarding this, I...

I agree, `mount` should read it from the metadata (where I believe it's stored), and `format` should take it as parameter.

Missing upstream: https://github.com/ARMmbed/littlefs/issues/349

Hey, thanks for your interest. You don't need `no_std` (cf. https://docs.rs/memchr/2.4.1/memchr/#crate-features), we use this in https://github.com/solokeys/solo2/tree/main/runners/lpc55. I think if you link to https://github.com/solokeys/solo2/tree/main/components/c-stubs in your dependencies it might just work,...

I remembered... In this commit: https://github.com/nickray/littlefs2/commit/cdcb99fea7a53f59e582d0b3702c5bae432a8db3 I removed a workaround for fact that the bindgen build dependency (of `littlefs2-sys`) triggers the `std` feature of `memchr`. However, with a new `cargo`...