In general, using bare integers in bit vector context is error-prone because the width of the integer, when cast to a Value, will change with its value. Values other than 0 and 1 are very likely to indicate a potential issue. Whether we want to allow 0 and 1 is an open question, but I suspect that people are relying on that.
The text was updated successfully, but these errors were encountered:
I've definitely used 0 and 1 inside Cat a bunch for adding an extra bit, in situations like the UART example where it's convenient for shift registers, but it's not that bad to use Const either. I think the meaning is pretty clear with 0 and 1 though.
I checked and about 10% of my Cat calls use a bare 0 or 1.