Paul Querna

It is a bug -- as `encoding/json` would error, so should `ffjson`, we want to be a drop-in replacement in as many cases as possible.

The performance numbers are inline for 'real world' structures, eg goser: https://github.com/pquerna/ffjson/blob/master/tests/goser/ff/goser.go and go.stripe: https://github.com/pquerna/ffjson/blob/master/tests/go.stripe/ff/customer.go I'm happy to add more structures -- ideally ones used in real world projects --...

It might be easier to focus on removing/converting the invocations of `WriteJsonString` to `WriteJson` in the generated code, a couple places i looked, we were actually converting a []byte into...

hmm. i guess we can should try to match argv paths to any matching $GOPATH, rather than just chopping the first $GOPATH entry. @tcurdt: if you change your $GOPATH to...

hmm. where did you 'learn' to $GOPATH? the `src/` org is what golang docs officially do now, `go get` implements, etc

+1, its reasonable to do this at compile time if we can -- we could think of it as anywhere `json.Marshal` would of `panic(...)` or returned an `error`, if we...

+1, we always want to maintain the "drop-in"-ness for the core of ffjson -- I'd be OK long run having an explicit `ffjson-extensions` module maybe, but the default experience has...

I've also switched to using a newer version of PyPy... which broke, so I switched to Portable PyPy: https://gist.github.com/pquerna/eb95ad6884a0cdd8dcb8 https://github.com/squeaky-pl/portable-pypy

(upstream package here) BTW, I'm generally fine adding support for this in cachecontrol, but as someone who has been doing http caching for a long time, I wasn't familiar with...

https://github.com/cavaliercoder/go-rpm provides native go code for dealing with RPM file format and parts of YUM which would be useful for this project.