From: ennder via ruby-core <ruby-core@...>
Date: 2025-02-02T01:15:05+00:00
Subject: [ruby-core:120856] [Ruby master Feature#21105] Improve Ruby Stack Trace to Include Exact Error Position (Column Number)

Issue #21105 has been reported by ennder (J�r�me BATAILLE).

----------------------------------------
Feature #21105: Improve Ruby Stack Trace to Include Exact Error Position (Column Number)
https://bugs.ruby-lang.org/issues/21105

* Author: ennder (J�r�me BATAILLE)
* Status: Open
----------------------------------------
h2. Subject
Improve Ruby Stack Trace to Include Exact Error Position (Column Number)

h2. Description
Currently, when an exception occurs in Ruby, the stack trace provides the file name and line number but does not indicate the exact position (column number) where the error occurred within the line. This lack of precision can make debugging more challenging, especially in cases where multiple method calls or expressions are present on the same line.

h2. Example

<pre><code class="ruby">
class Example
  def self.run
    nil.some_method_call  # Error occurs here
  end
end

Example.run
</code></pre>

h2. Expected Behavior

The stack trace should include the column number where the error occurred, e.g.:
<pre><code>
trace.rb:4:10:in `run': undefined method `some_method_call' for nil:NilClass (NoMethodError)
</code></pre>

h2. Benefits

More precise debugging.

Easier identification of errors in complex one-liner expressions.

Better tooling support for editors and debuggers.

h2. Additional Notes
Would it be possible to add this enhancement in a future Ruby version?

Thank you for considering this request!




-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/