Closed azw413 closed 2 years ago
This one is a pretty confusing one, I'll have to dig a little further on it. When I dump it into a test for res-regex
it overflows the u32
so it seems like there are some issues for sure with the parsing (hopefully not the tokenizing)
This should now be fixed, cargo update -p res-regex
to get >= 0.1.4
Thanks Robert ! I confirm that it can now parse that line.
I found a parse error in the following line of code:
The error is
Other(Error { msg: "numbers out of order in {3675569185,2395953488}", idx: 121 })