ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "Eregon (Benoit Daloze) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "Eregon (Benoit Daloze)" <noreply@ruby-lang.org>
Subject: [ruby-core:119196] [Ruby master Bug#20736] prism emits wrong warnings in syntax-error code
Date: Sun, 15 Sep 2024 10:25:26 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-109780.20240915102525.18@ruby-lang.org> (raw)
In-Reply-To: <redmine.issue-20736.20240913032332.18@ruby-lang.org>

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


I think good error recovery is key to have helpful error messages when writing Ruby code.

Maybe one way here is to not show warnings if there are any errors?
OTOH I think it is not a big usability problem, warnings appear first and the separation between warnings and errors is clear in the output.
(and parse.y also shows both warnings and errors when there are both, as shown above)

> However, I am not sure about the benefit, given the such confusing warnings.

These are very synthetic examples in test.
What matters is how helpful is the output for code (with errors) that users would write.

So I think setting $VERBOSE to nil in these tests is the right fix.
It's also what is done e.g. [here](https://github.com/ruby/rdoc/blob/964a1982c8387881a61fc7855a3b999ffdc191b6/lib/rdoc/markup/to_html.rb#L434-L443).

> If other problems arise, we should stop error recovery in the interpreter.

Let's not jump to such conclusions because some synthetic code in a test emits some confusing output, that code is confusing in the first place.
Instead, I propose we evaluate based on code written by humans and not generated by tests.

----------------------------------------
Bug #20736: prism emits wrong warnings in syntax-error code
https://bugs.ruby-lang.org/issues/20736#change-109780

* Author: mame (Yusuke Endoh)
* Status: Feedback
* Assignee: kddnewton (Kevin Newton)
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
```
$ ./local/bin/ruby -w --parser=parse.y -e 'begin eval("0a"); rescue SyntaxError; end'
$ ./local/bin/ruby -w --parser=prism -e 'begin eval("0a"); rescue SyntaxError; end'
(eval at -e:1):1: warning: possibly useless use of a literal in void context
```

```
$ ./local/bin/ruby -w --parser=parse.y -e 'begin eval("+a.0"); rescue SyntaxError; end'
$ ./local/bin/ruby -w --parser=prism -e 'begin eval("+a.0"); rescue SyntaxError; end'
(eval at -e:1):1: warning: possibly useless use of +@ in void context
```




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

      parent reply	other threads:[~2024-09-15 10:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13  3:23 [ruby-core:119163] " mame (Yusuke Endoh) via ruby-core
2024-09-13 15:32 ` [ruby-core:119178] " kddnewton (Kevin Newton) via ruby-core
2024-09-13 19:51 ` [ruby-core:119187] " mame (Yusuke Endoh) via ruby-core
2024-09-13 20:59 ` [ruby-core:119188] " kddnewton (Kevin Newton) via ruby-core
2024-09-15  0:46 ` [ruby-core:119192] " mame (Yusuke Endoh) via ruby-core
2024-09-15  0:51 ` [ruby-core:119193] " mame (Yusuke Endoh) via ruby-core
2024-09-15 10:25 ` Eregon (Benoit Daloze) via ruby-core [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=redmine.journal-109780.20240915102525.18@ruby-lang.org \
    --to=ruby-core@ml.ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).