goparsify [![CircleCI](https://circleci.com/gh/Vektah/goparsify/tree/master.svg?style=shield)](https://circleci.com/gh/Vektah/goparsify/tree/master) [![godoc](http://b.repl.ca/v1/godoc-reference-blue.png)](https://godoc.org/github.com/Vektah/goparsify) [![Go Report Card](https://goreportcard.com/badge/github.com/vektah/goparsify)](https://goreportcard.com/report/github.com/vektah/goparsify) ========= A parser-combinator library for building easy to test, read and maintain parsers using functional composition. Everything should be unicode safe by default, but you can opt out of unicode whitespace for a decent ~20% performance boost. ```go Run(parser, input, ASCIIWhitespace) ``` ### benchmarks I dont have many benchmarks set up yet, but the json parser keeps up with the stdlib for raw speed: ``` $ go test -bench=. -benchtime=2s -benchmem ./json BenchmarkUnmarshalParsec-8 50000 66012 ns/op 50462 B/op 1318 allocs/op BenchmarkUnmarshalParsify-8 100000 46713 ns/op 44543 B/op 332 allocs/op BenchmarkUnmarshalStdlib-8 100000 46967 ns/op 13952 B/op 262 allocs/op PASS ok github.com/vektah/goparsify/json 14.424s ``` ### debugging parsers When a parser isnt working as you intended you can build with debugging and enable logging to get a detailed log of exactly what the parser is doing. 1. First build with debug using `-tags debug` 2. enable logging by calling `EnableLogging(os.Stdout)` in your code This works great with tests, eg in the goparsify source tree ``` $ cd html $ go test -tags debug -parselogs html.go:50 |
hellohello
hello
hello
hello
hello
hello
| > html.go:26 | hello
| < | < html.go:20 | color="blue">w | p | identifier html.go:35 | color="blue">w | | attrs html.go:34 | color="blue">w | | attr html.go:20 | ="blue">world | color | identifier html.go:34 | "blue">world
worldworldworld | > html.go:26 | world