Drew Boyuka
Drew Boyuka
I've been thinking of prototyping this feature, as well. If I get some free time over the next couple days I may look at your code and spin something off...
In my opinion, it should return an `error` instead, and that `error` should be passed through to the caller of `ArrayEachLimited`.
True, but `error` is more versatile. You could return `io.EOF` to signal "done iterating, no problem" to your outer code.
This looks really cool. Thanks for keeping the offset-computing code separate so as to not slow down the simpler `searchKeys` case (this is nice for me since I'm not sure...
What if you made a wrapper around the core functions for a more user-friendly experience? E.g.: ``` lookup := NewMultiKeyLookup(data) refs := lookup.MultiGet( []string{"a"}, []string{"b"}, []string{"c"}, ) val1 := lookup.Get(ref[0])...
Doh, you're right, I guess I meant `refs :=` and then `refs[0]`, etc. Edited.
The difference between `ArrayEach` and `ObjectEach` is an artifact of this library's API evolution over time, unfortunately. `EachKey` actually does something fundamentally different from the other two (it's basically a...