fix: ensure VALUE_MIN is strictly a value_t
For some reason, in f5c8cc54 we did not switch the lower limits of unsigned types to also use the _fast_ variants. I don't think this caused any correctness issues, but it may be the cause of some current -Wsign-compare warnings with tests/for-step-0-dynamic.m.
parent
efeae830
Please register or sign in to comment