Ayke
Have you tested this with UART1/UARTE1? I think receiving won't work currently because it is missing an interrupt handler for `UARTE1`.
I think the easiest way forward would be to use UART on the nrf51 and UARTE on all the nrf52 chips. That means that the implementations on both families are...
Circular buffering does not seem to be possible (looking at the datasheet), but this might be done manually. For example, with a receive buffer of (say) 16 bytes where bytes...
I'm not sure I agree with this change. I've considered it before but rejected the idea because while it gets the encoding/json package to mostly work, it is somewhat incorrect.
Specifically, what I'm worried about with this PR is that it is not correct for named types. For unnamed types it seems to be correct (it just returns the underlying...
> Is it possible to proceed with this, even if a longer term, larger PR may happen in the future? I still don't agree with merging incorrect code. This PR,...
You can compile to an object file by giving it an `.o` extension. But it will likely lack some symbols you need. Alternatively, you can use Go and include external...
Yes, `GOARM` is different but it has no effect on the binaries. It is only used when creating native linux/arm binaries. For example: ``` $ GOOS=windows tinygo info "" LLVM...
Closing in favor of #2954
Call parameter type does not match function signature! when method input parameter is a generic type
See: https://github.com/tinygo-org/tinygo/pull/2998