inconsistent use of min/max is inclusive #260
At revision 1.1, the mixed case MinIsInclusive and MaxIsInclusive were changed to all lower case- the document now contains two different column references for each:
This needs to be corrected - all lower case is the change that was to be made.
The text was updated successfully, but these errors were encountered:
That’s the only place I see it as well. Simple editorial fix should suffice.
From: Jeff Yutzler [mailto:firstname.lastname@example.org]
@KRydenhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_KRyden&d=DQMCaQ&c=n6-cguzQvX_tUIrZOS_4Og&r=tvLPjeMfOs5jYGz-2NsVow&m=6sip7lsmeQeP18iADu4IKQCufF0pGZD3XEzhevw-msc&s=8w9fBBOtOsLhYraSPz3w0RGLuSu42YY5aD_6swF25HY&e= I am only seeing minisinclusive in the abstract tests. That is a pretty easy fix.