jaxter184

I've made the requested changes On combining the crates, these two chips are unfortunately pretty different (different number of pins, different peripherals), so I don't think it would make sense...

|| t841 | t861 | |-|-|-| |gpio|a|a,b| |timer|1x 8bit, 2x 16bit|1x 8bit, 1x 16/8bit hybrid| |adc|10bit|10bit| |ac|2x|1x| |comms|SPI,I2C (slave only), 2x USART|USI| The biggest difference is the serial communication options....

[This wikipedia article](https://en.wikipedia.org/wiki/ATtiny_microcontroller_comparison_chart) groups the ATtinys into 4 groups (not including the newer generation, which is pretty clear about its grouping). I'm not sure what exactly the process is for...

Seems to me like all the relevant information has been collected, and all that's left is to make a decision. I'm not sure if this assumption has already been made,...

Glad to hear the decision has been made! Just to clarify, are the newer series-0/1/2 chips getting their own category? and if so, are they each getting a crate or...

The [i2c scanner example in the stm32f3xx-hal](https://github.com/stm32-rs/stm32f3xx-hal/blob/master/examples/i2c_scanner.rs) may be a good reference for including a practical i2c example that doesn't depend on any connected devices

Looks neat, I think the event-based communication makes the most sense, though my worry is that it might not be zero-cost (or at least as low-cost as it can be)?...

> Maybe just the hardware initialization for an I2C peripheral in "slave mode" should be part of the HAL, and any SMBus/I2C slave library can work with that. Just a...

> I wonder if a happy medium might be allow implementations to supply their own error type, but to require that error type implement Into. Makes sense, maybe this is...

I don't think the enter hotkey solves this issue in all cases. For one, it's not very clear what the hotkey is, or that it even exists. Most programs use...