Daniel Egger

Sure. But maybe if you want to have a proper I2C slave you should try to prioritise the functionality required for an I2C slave first?

Not really sure how that happened but: ``` # cargo tree -i [email protected] http v1.0.0 ├── actix-tls v3.3.0 │ ├── actix-http v3.6.0 │ │ ├── actix-web v4.5.1 │ │ │...

I think switching to and using a 1.0 version is always a good venture due to the implied stability guarantees.

> It looks like we do have an existing assert for this. For me, in debug builds, I get a panic. Yes, this is mentioned in the bug report above....

> `bool` is defined in the reference to [default to flag-like behavior](https://docs.rs/clap/latest/clap/_derive/index.html#arg-types) and you need to override what clap is doing implicitly. Not sure I understand. I do want that...

> Are you wanting a flag or a positional value? I don't really care, I was hoping for a positional (the documentation in https://docs.rs/clap/latest/clap/_derive/index.html#arg-types does call the effect a flag...

I think at least the documentation could be clarified to point out that pitfall and maybe provide an example for positional bool.

@gbip I'm not a big fan of this approach. The memory configuration should always be on a per application basis because you might want to have RAM/Flash excluded for specific...

@aurabindo You mean as an extension of the `embedded-hal` traits? Sounds like a good idea, feel free to propose it over at: https://github.com/rust-embedded/embedded-hal

@aurabindo Yes, in a way you're right but that's nothing **you** should have to worry about. First I'd recommend opening a ticket describing what functionality you'd like to achieve. Then...