Patricio Whittingslow

I wasn't aware of it before but working with float32 slices can speed up programs in certain cases since more data fits on a cache line.

Can we specify what assembly implementations should be added?

We should create issues regarding what assembly specializations are required. I'll close this one if no one objects so we can focus work on issues which target a specific architecture...

Hey sorry for the long wait, not sure how this slipped my radar. I've added a fix to exclude all assembly from tinygo builds. Let me know if this solves...

Fixed in latest version v1.11.0- the Go tool was not picking up v1.11 tag because it was missing the minor version to qualify as semantic versioning. Running `go get -u...

Heads up, latest commit in PIO repository has a working WS2812B implementation. I've tested it on a strip and it works pretty well, with or without DMA. https://github.com/tinygo-org/pio/blob/main/rp2-pio/examples/ws2812b/main.go

Another take: ```go // GetPWM acquires a unconfigured [PWM instance]. The returned PWM // should be configured before use. e.g: // // pwm, channel, err := GetPWM(machine.GP20) // if err...

> I think it would be possible to add a Pin.SetPWM Hrmm, this would not solve my API case, though let me sit on it and see if maybe it...

For posterity, here's the code as would be used: ```go package main import ( "machine" "time" ) // Add your PWM pins here. var pwmPins = [...]machine.Pin{ machine.GP0, machine.GP3, machine.GP4,...

After reading some [termios stuff](http://unixwiz.net/techtips/termios-vmin-vtime.html) it seems this is not expected functionality: If `VMIN` is zero then the function should be a purely timed function and return after 1 second.