Because it's contained in one method, it short circuits processing when a
nil occurs whereas the Gets will look at each item. Also less function
context switches which I'm hoping will be better performance when deeply
nested json which a large concurrent access.

Optional for you to add but because I'm dealing with large number of
accesses I need whatever boost I can get.

Thanks
Leon
On 3 Apr 2013 09:26, "Matt Reiferson" <notifications@github.com> wrote:

> In simplejson.go:
>
> > @@ -56,6 +78,27 @@ func (j *Json) Get(key string) *Json {
> >  	return &Json{nil}
> >  }
> >
> > +// Find searches for the item as specified by the branch without the need to
> > +// deep dive using Get()'s. Returns nil if not found.
> > +//
> > +//   js.Find([]string{"top_level", "dict"})
> > +func (j *Json) Find(branch []string) *Json {
>
> same thing here, not quite sure im sold on this one... can you describe a
> context where this is easier than just using Get()?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/bitly/go-simplejson/pull/12/files#r3628564>
> .
>