Joshua Warner 2d9aba2242 Refactor parser methods to not return State as part of ParseError ... As previously discovered with #4464, it's easy to accidentally mis-use the State value returned on the Err path. There were mixed assumptions about what that State represents: (1) the State where the error occurred, or (2) the State at the beginning of the thing we were just parsing. I fixed this up to always mean (2) - at which point we don't actually need to return the State at all - so it's impossible for further discrepency to creep in. I also took the liberty to refactor a few more methods to be purely combinator-based, rather than calling `parse` directly.		2022-11-18 19:52:23 -05:00
..
cli_gen.rs	Fix error filtering region math	2022-11-01 01:20:52 -04:00
colors.rs	Drop the gray lines from the repl	2022-11-01 22:05:47 -04:00
lib.rs	merge upstream/main	2022-11-06 09:27:46 +11:00
repl_state.rs	Refactor parser methods to not return State as part of ParseError	2022-11-18 19:52:23 -05:00