Issue #14558 has been updated by gfx (Goro FUJI).


mrkn (Kenta Murata) wrote:
> > it sometimes "reversed", sometimes "non-reversed"
> 
> Is it acceptable that the backtrace is always new, 2.5-style order?

Might be acceptable, or at least it's better than the current "random" order.


Why not provide a way to customize it, for example `RubyVM.backtrace_reverse_order = -> (io) { true }`, where  `-> (io) { io.tty? }` is the algorithm that 2.5.0 has.

----------------------------------------
Bug #14558: "Backtrace in reverse order" always upsets my brain!
https://bugs.ruby-lang.org/issues/14558#change-70715

* Author: gfx (Goro FUJI)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin16]
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
A Ruby 2.5.0 feature "backtrace in reverse order", issued in https://bugs.ruby-lang.org/issues/8661, is confusing in developing Rails applications because I can't expect the order: it sometimes "reversed", sometimes "non-reversed". It just sucks.

Please revert this feature, or provide a way to disable it.




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>