Patricio Whittingslow

> good idea Help me out Ron. The more I think about this the more this is outweighed by the benefits of function pointer API. We are very lucky to...

> How will it break, @soypat? I must be missing something. (See code below if this is not clear) Before this change drivers were initialized with `machine.Pin` type and as...

I've gained another worry in the last few hours regarding this PR. I've recently been looking at lots of C drivers to write up my driver design document. When looking...

I've worked on codebases with 3 pin implementations, and that was a small project by the comapany's standards: - Typical `machine.Pin` implementation - One implementation that required cycle synchronised pulse...

Heck I forgot the board was going to add a fifth pin HAL as well with a GPIO multiplexer. And I can't guarantee it would've stopped there.

Kept thinking and there are several use cases in the TinyGo ecosystem that would be affected. Use cases which would negatively be affected by the interface slowdown : - Bitbang...

OK, nice! I feel we are reaching some common ground! :smile: I feel like we are close to a compromise between PinFuncs and drivers.Pin but that there are details being...

@ysoldak I'll remind you we agreed with @aykevl to revise a proposed change with no implied breakage; the PR with proposed changes is here https://github.com/tinygo-org/drivers/pull/753. I'd really like some feedback/input...

Just a friendly reminder, and best to leave it persisted in this conversation, that we agreed to go with the more conservative approach in #753 and leave this open for...

If you are to use the `net` API you need to set the Netdever by calling UseNetdev: https://github.com/tinygo-org/drivers/blob/019bbbe5fb66ff6ecd50949520253a50ecc72733/netdev/netdev.go#L56 That said, that is much easier said than done without a NetDever....