Feature #5016: Kernel#caller with negative limit should limit result to N initial frames

• Status: Closed
• Assignee: ko1 (Koichi Sasada)
• Target version: 2.0.0

[now (Nikolai Weibull)]

Calling Kernel#caller with a negative limit should limit result to N initial frames. When using Kernel#caller you often only want the first element of the result to get the information of the immediate caller. Generating the whole backtrace in this case is wasteful and time-consuming. Allowing Kernel#caller to take a negative limit to only return the first -N initial stack frames would allow for this.

[ddebernardy (Denis de Bernardy)]

Dup of #1906 and #3917.

[now (Nikolai Weibull)]

I wouldn’t say “dup”, but it’s certainly related. This interface can be used instead of adding Kernel#called_from, if we want to keep the number of methods down. Also, even if we objectify the backtrace as per #1906 that still doesn’t mean that we shouldn’t have the limit as per this feature request.

[mame (Yusuke Endoh)]

• Status changed from Open to Assigned
• Assignee set to ko1 (Koichi Sasada)

[ko1 (Koichi Sasada)]

Calling Kernel#caller with a negative limit should limit result to N initial frames. When using Kernel#caller you often only want the first element of the result to get the information of the immediate caller. Generating the whole backtrace in this case is wasteful and time-consuming. Allowing Kernel#caller to take a negative limit to only return the first -N initial stack frames would allow for this.

There are similar proposals.
https://bugs.ruby-lang.org/issues/3917

Maybe there are other proposals. I want to summarize and implement 2.0.
At first, I want to know other alternative proposals. Please let me know.

--
// SASADA Koichi at atdot dot net

[ko1 (Koichi Sasada)]

• Status changed from Assigned to Closed

See https://bugs.ruby-lang.org/issues/3917