Rahix

The proc-macro2 vs nightly rustc story is also a whole other minefield on top, see https://github.com/Rahix/avr-device/pull/156 as well.

@LuigiPiucco, I have finally merged the new toolchain here and in `avr-hal`, so we can go full steam ahead with the final build-out of this PR. I'm sorry for all...

> I'm working on refactoring the error handling of this PR, would you prefer I amend it here once finished, or that I open a separate one after merge? It...

Unfortunately, this is not yet supported in the HAL. You can of course implement this by directly interfacing with the registers, but there is no nice abstraction for it yet......

I have a usecase for parity/framing errors. In [profirust](https://github.com/Rahix/profirust) (a PROFIBUS-DP communication stack) it would be nice to differentiate between "receiving nothing" and "receiving an invalid character" for error statistic...

Very nice, I like this feature a lot! > Chamfers don't work with thin plates; the walls are too thin at the corners. So it might be better to always...

> I don't have a good answer for the 1x1 plates yet. I think the best option is to either drop the magnet holes for 1x1 baseplates because there is...

ping @EmperorArthur :) (also for #301) > 1x1 baseplates are useful for test prints and some "This tool goes here" things. Though, I don't know enough about your PR to...

I think it would be valuable to have something like Linux' regmap API ([only introduction I could quickly find](https://www.opensourceforu.com/2017/01/regmap-reducing-redundancy-linux-code/)) to abstract away the bus details in device drivers. This could...

This becomes superfluous with #157 on the horizon. Will close this issue once that PR is merged.