Matt Reiferson

The end-user provides the channel to send to, it's entirely up to them to provide buffered channels so that the calls won't block.

looks fine otherwise, API bloat aside. We really need to think about `go-simplejson` 2 at some point :grin:

How about writing up an issue with your proposed changes/API here on this repo so we can plan the next version?

nice work @AzuraMeta another naming suggestion. I think `Json` should be `JSON`.

also, since we only really ever generate our own errors, it's possible that the `Check*` methods should return `(*JSON, bool)` rather than `(*JSON, error)`, since it isn't incredibly useful.

It needs to use that for big numbers, I think.

this is looking great! FWIW I meant _all_ instances of `Json` to `JSON`. This made me realize one path forward - we could keep both types in this package (the...

1. I don't think `Set` needs to mirror the "path" functionality of `Get`, if that's what you mean. 2. I think you are correct, `Set` needs to "unpack" `*Json`

I don't _think_ so, but I'm open to other opinions

Not explicitly, no. That `destroy()` method you linked to will execute when Go's garbage collector decides to clean up that object. When nothing references the bloom filter pointer it will...