[#112457] [Ruby master Feature#19443] Cache `Process.pid` — "byroot (Jean Boussier) via ruby-core" <ruby-core@...>
Issue #19443 has been reported by byroot (Jean Boussier).
16 messages
2023/02/16
[#112584] [Ruby master Feature#19465] [PATCH] reuse open(2) from rb_file_load_ok on POSIX-like system — "normalperson (Eric Wong) via ruby-core" <ruby-core@...>
Issue #19465 has been reported by normalperson (Eric Wong).
9 messages
2023/02/25
[#112595] [Ruby master Feature#19465] [PATCH] reuse open(2) from rb_file_load_ok on POSIX-like system
— "nobu (Nobuyoshi Nakada) via ruby-core" <ruby-core@...>
2023/02/25
SXNzdWUgIzE5NDY1IGhhcyBiZWVuIHVwZGF0ZWQgYnkgbm9idSAoTm9idXlvc2hpIE5ha2FkYSku
[#112613] Re: [Ruby master Feature#19465] [PATCH] reuse open(2) from rb_file_load_ok on POSIX-like system
— Eric Wong via ruby-core <ruby-core@...>
2023/02/26
"nobu (Nobuyoshi Nakada) via ruby-core" <ruby-core@ml.ruby-lang.org> wrote:
[#112615] Re: [Ruby master Feature#19465] [PATCH] reuse open(2) from rb_file_load_ok on POSIX-like system
— SHIBATA Hiroshi via ruby-core <ruby-core@...>
2023/02/27
MzUxMzZlMWU5YzIzMmFkN2EwMzQwN2I5OTJiMmU4NmI2ZGY0M2Y2MyBpcyBicm9rZW4gd2l0aCBg
[#112626] Re: [Ruby master Feature#19465] [PATCH] reuse open(2) from rb_file_load_ok on POSIX-like system
— Eric Wong via ruby-core <ruby-core@...>
2023/02/28
```
[ruby-core:112519] [Ruby master Feature#19451] Extract path and line number from SyntaxError?
From:
"ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>
Date:
2023-02-21 03:43:06 UTC
List:
ruby-core #112519
Issue #19451 has been updated by ioquatix (Samuel Williams). @nobu most text editors need a single line and column for each backtrace location. As it stands, just looking at the backtrack locations is not enough. For `SyntaxError`, the editor needs to know the "first location" which is the point the syntax error occurred. There are two ways this can be done: (1) SyntaxError#path / #line / #column information + SyntaxError#backtrace_locations (2) SyntaxError#backtrace_locations[0] contains the above `#path` `#line` and `#column` information, followed by the normal backtrace. By "prepend them to the backtrace_locations" I mean option (2), which is far easier for the editor to consume, since it won't have to know the specific details of how "SyntaxError" works, it will just put markers at each `backtrace_locations`, with the error details itself on `backtrace_locations[0]`. ---------------------------------------- Feature #19451: Extract path and line number from SyntaxError? https://bugs.ruby-lang.org/issues/19451#change-101963 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal ---------------------------------------- There doesn't seem to be any official way to extract the path and line number from a syntax error. There are two ways I can see us dong this: - Provide explicit `path` and `line_number` attributes. - Prepend them to `backtrace_locations`. The nice thing about the latter approach is that it will just work with existing tools which understand how to highlight code based on backtrace locations. Maybe we should do both? -- 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/postorius/lists/ruby-core.ml.ruby-lang.org/