Ayke

@vanrein thank you for the suggestion! I haven't worked much on the net package but will keep it in mind as an option.

What about pull up and down? It seems to me that those are rather important and also supported on most chips (I believe AVR is an exception and it only...

Also, what problem are you trying to solve exactly? Adding `PinConfigInput` and `PinConfigOutput` (returning a `machine.PinConfig`) do not remove a dependency on the `machine` package.

Ah okay, thank you for the explanation. I'm not entirely convinced that adding more API surface will simplify things, to be honest. However, the current API is a bit more...

Although, maybe the suggestion from @conejoninja is better as it also allows using the pins in an interface. For example, a hypothetical button driver could use this interface: ```go type...

What do you mean, default? There are three possible ways to configure an input: with a pulldown, a pullup, and floating. `machine.PinInput` configures the input as a floating input and...

@QuLogic thanks! I have now rebased and updated it after multiple changes in the dev branch (mostly generics and timers). Right now I have a local branch that adds support...

@deadprogram looks like the TinyHCI runner might need a Go update.

Yes, the timers test is flaky on MacOS.

Hmm, this suggests some sort of memory error or race condition in the compiler. Can you try rebuilding LLVM with assertions enabled? It might surface the actual bug.