Closed bstexas closed 5 years ago
When escapes aren't taken into account in source string, erratic behavior is encountered when comparing with CPESet2_3._compare_strings:
Coverage remained the same at ?% when pulling 9aa803b402d1f6cdeda011a1a3d98bf8808556a6 on bstexas:develop into 670d947472a7652af5149324977b50f9a7af9bcf on nilp0inter:develop.
Thanks!
When escapes aren't taken into account in source string, erratic behavior is encountered when comparing with CPESet2_3._compare_strings: