ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
* [ruby-core:120856] [Ruby master Feature#21105] Improve Ruby Stack Trace to Include Exact Error Position (Column Number)
@ 2025-02-02  1:15 ennder via ruby-core
  2025-02-02 11:42 ` [ruby-core:120861] " Eregon (Benoit Daloze) via ruby-core
  0 siblings, 1 reply; 2+ messages in thread
From: ennder via ruby-core @ 2025-02-02  1:15 UTC (permalink / raw)
  To: ruby-core; +Cc: ennder

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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [ruby-core:120861] [Ruby master Feature#21105] Improve Ruby Stack Trace to Include Exact Error Position (Column Number)
  2025-02-02  1:15 [ruby-core:120856] [Ruby master Feature#21105] Improve Ruby Stack Trace to Include Exact Error Position (Column Number) ennder via ruby-core
@ 2025-02-02 11:42 ` Eregon (Benoit Daloze) via ruby-core
  0 siblings, 0 replies; 2+ messages in thread
From: Eregon (Benoit Daloze) via ruby-core @ 2025-02-02 11:42 UTC (permalink / raw)
  To: ruby-core; +Cc: Eregon (Benoit Daloze)

Issue #21105 has been updated by Eregon (Benoit Daloze).


It is already shown:
```ruby
class Example
  def self.run
    nil.foo.bar.baz
  end
end

Example.run
```

```
example.rb:3:in `run': undefined method `foo' for nil (NoMethodError)

    nil.foo.bar.baz
       ^^^^
	from example.rb:7:in `<main>'
```

Adding columns would add a lot of noise and would not be clearer than that.
So I think we can close this as "already done, just in a different/clearer way"

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

* Author: ennder (Jérôme BATAILLE)
* Status: Open
----------------------------------------
## Subject

Improve Ruby Stack Trace to Include Exact Error Position (Column Number)

## 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.

## Example

``` ruby
class Example
  def self.run
    nil.some_method_call  # Error occurs here
  end
end

Example.run
```

## Expected Behavior

The stack trace should include the column number where the error occurred, e.g.:

``` ruby
trace.rb:4:10:in `run': undefined method `some_method_call' for nil:NilClass (NoMethodError)
```


## Benefits

More precise debugging.

Easier identification of errors in complex one-liner expressions.

Better tooling support for editors and debuggers.

## 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/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2025-02-02 11:42 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-02-02  1:15 [ruby-core:120856] [Ruby master Feature#21105] Improve Ruby Stack Trace to Include Exact Error Position (Column Number) ennder via ruby-core
2025-02-02 11:42 ` [ruby-core:120861] " Eregon (Benoit Daloze) via ruby-core

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).