Julien Cretin

> [Max erase is] a property that is good to know, but does this make much practical sense? The way I use it is to provide the library user with...

> Each of these lines would probably be a single trait The problem of doing this is explained in this comment: https://github.com/rust-embedded-community/embedded-storage/pull/22#issuecomment-1008300181. Ideally, there would be a single trait to...

> sequential writing Very interesting, thanks for the concept. I wasn't aware of this. It's good to know, I can easily adapt my library design for this. I already write...

I think we should distinguish the following 2 properties and not merge them: - How many times a block can be written and under which conditions (e.g. can be written...

> If after having "no rewrites unless it is with 0" (possibly "or identical") there is still a use case around for "no rewrites but identical doesn't count", sure we...

What is the soundness argument for this error? A reason why I believe this is sound: ```rust // For every function foo like fn foo &'long mut T { ......

Thanks for the suggestion! I think it makes sense to do something like that however: 1. I won't have time to work on it before mid June. 2. I'm not...

As expected, making `{encode,decode}_len` const fns does not work for a few different reasons: - I use traits and it's not possible to have `const fn` in traits. - I...

You can test if #70 is fixing your issue. Instead of writing `let buf = [0u8; BASE64.encode_len(32)];` as in your original comment, you would need to write `let buf =...

Due to lack of activity I'm going to close this. This will eventually get fixed once const support in Rust is improved.