mirror of https://github.com/tinygo-org/tinygo.git
Browse Source
As discussed on Slack, I believe this property does more harm than good: * I don't think it's used anywhere. None of the drivers use it. * It is not fully implemented. While values <= 8 might work fine, values larger than 8 result in extra zero bits (instead of anything sensible). * Worse, it doesn't return an error when it's out of range. This is not an optional property: if the SPI peripheral doesn't support a particular number of bits, it should return an error instead of silently limiting the number of bits. This will be confusing to users. Therefore, I propose we drop it. Maybe there are good uses for it (perhaps for displays that use big endian 16-bit values?), but without a good use case like a driver in tinygo.org/x/drivers, I think it's more trouble than it's worth.pull/3301/head
Ayke van Laethem
2 years ago
committed by
Ron Evans
1 changed files with 3 additions and 8 deletions
Loading…
Reference in new issue