Wilson Bilkovich wrote:
> I much prefer 'location', because it is something that every Ruby
> implementation can provide. iseq is super super low-level, and we
> should think hard about the API before calling it public.

I would also hope any "location" methods added will refer only to static 
information, like the place the Proc was created, rather than adding yet 
another method with "special" knowledge of the caller's context 
(requiring the ability to look across invocation frames).

- Charlie