From: "ko1 (Koichi Sasada)" Date: 2012-06-26T05:25:57+09:00 Subject: [ruby-core:45853] [ruby-trunk - Feature #5016][Closed] Kernel#caller with negative limit should limit result to N initial frames Issue #5016 has been updated by ko1 (Koichi Sasada). Status changed from Assigned to Closed See https://bugs.ruby-lang.org/issues/3917 ---------------------------------------- Feature #5016: Kernel#caller with negative limit should limit result to N initial frames https://bugs.ruby-lang.org/issues/5016#change-27440 Author: now (Nikolai Weibull) Status: Closed Priority: Normal Assignee: ko1 (Koichi Sasada) Category: core Target version: 2.0.0 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. -- http://bugs.ruby-lang.org/