mentat/tx-parser
Nick Alexander cbffe5e545 Use rust-peg for tx parsing.
There are few reasons to do this:

- it's difficult to add symbol interning to combine-based parsers like
  tx-parser -- literally every type changes to reflect the interner,
  and that means every convenience macro we've built needs to chagne.
  It's trivial to add interning to rust-peg-based parsers.

- combine has rolled forward to 3.2, and I spent a similar amount of
  time investigating how to upgrade tx-parser (to take advantage of
  the new parser! macros in combine that I think are necessary for
  adapting to changing types) as I did just converting to rust-peg.

- it's easy to improve the error messages in rust-peg, where-as I have
  tried twice to improve the nested error messages in combine and am
  stumped.

- it's roughly 4x faster to parse strings directly as opposed to
  edn::ValueAndSpan, and it'll be even better when we intern directly.
2018-05-10 10:24:05 -07:00
..
benches Use rust-peg for tx parsing. 2018-05-10 10:24:05 -07:00
src Add TransactableValue abstracting value places that can be transacted. 2018-05-10 10:19:54 -07:00
tests Post: Reject at parse-time reversed attributes in direct notation with bad values. 2017-06-08 10:30:31 -07:00
benches.txt Use rust-peg for tx parsing. 2018-05-10 10:24:05 -07:00
benches2.txt Use rust-peg for tx parsing. 2018-05-10 10:24:05 -07:00
Cargo.toml Update some dependencies. (#492) r=etoop 2017-11-21 16:24:08 +00:00