ivmarkov

Sorry for the delay here, I plan to look at this over the upcoming weekend.

@dragazo Sorry for the delay. I'm finally looking into this as I (also) might need to introduce an `AnyAdcPin` instance (in addition to the existing `AnyIOPin`, `AnyInputPin`, `AnyOutputPin` ones) so...

Here's one speculation I have by reading the earlier comments: you are essentially implementing an `ESPHome` or - like - `Tasmota` - if you like - except in Rust. What...

Is it possible to implement this functionality outside of `esp-idf-hal`? Even if it uses a little hidden `unsafe {}` here and there in its implementation? I fear that if we...

But your solution still seems incomplete. For one, I bet you currently have a very large `match` statement... in fact - multiple large `match` statements - one for each MCU...

> Actually I don't have any kind of big matches for that. All I do is convert the concrete pins into `AnyPin` and store them in a collection: https://github.com/dragazo/netsblox-vm-esp32/blob/638de2e35f1c6da37b1150ae2882cb79b47eaf47/src/platform.rs#L134-L178. But...

> It'd be great if we could just do the array version for everything like `peripherals.pins[5]` instead of `peripherals.pins.gpio5`. But sadly last I checked partial move semantics for arrays is...

Alright. I'll give it one last shot. :) > > Yeah. 48 lines of `pins.insert`. Same story. > > Well an array isn't going to construct itself when this crate...

I have mentioned in the comments above that this PR [has a much bigger scope](https://github.com/esp-rs/esp-idf-hal/pull/247#issuecomment-1612439027) than `AnyXXXPin`. A scope that is niche nevertheless. I have suggested an alternative which has...

No Bluetooth traits yet. Main two reasons - the ESP-IDF BT implementation is not "officially" exposed yet in `esp-idf-svc` - and - I don't have a good grasp of what...