Spec/implementation deviation in C protover code
Our C protover code will reject any attempt to create a protover range ending with UINT32_MAX. But our spec says that we allow that.
I suggest that, since this case is basically unreasonable, we should amend the spec to reject it, and amend the code to reject it explicitly.
Found by Teor.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information