ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "kddnewton (Kevin Newton) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "kddnewton (Kevin Newton)" <noreply@ruby-lang.org>
Subject: [ruby-core:117660] [Ruby master Bug#20449] Ripper issue in field production on Ruby 3.1.5
Date: Tue, 23 Apr 2024 19:44:09 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-20449.20240423194409.10206@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20449.20240423194409.10206@ruby-lang.org

Issue #20449 has been reported by kddnewton (Kevin Newton).

----------------------------------------
Bug #20449: Ripper issue in field production on Ruby 3.1.5
https://bugs.ruby-lang.org/issues/20449

* Author: kddnewton (Kevin Newton)
* Status: Open
* ruby -v: 3.1.5
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
```ruby
Ripper.sexp("foo::bar = baz")
# => [:program, [[:assign, [:field, [:vcall, [:@ident, "foo", [1, 0]]], 73, [:@ident, "bar", [1, 5]]], [:vcall, [:@ident, "baz", [1, 11]]]]]]
```

Note that 73 there. That's either `:"::"` or `[:@op, "::", [lineno, column]]` in every other version of Ruby that I could find. I assume this is a backport issue.



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

       reply	other threads:[~2024-04-23 19:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 19:44 kddnewton (Kevin Newton) via ruby-core [this message]
2024-04-23 20:45 ` [ruby-core:117662] [Ruby master Bug#20449] Ripper issue in field production on Ruby 3.1.5 rdimartino (Robert DiMartino) via ruby-core

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-list from there: mbox

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

  List information: https://www.ruby-lang.org/en/community/mailing-lists/

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

  git send-email \
    --in-reply-to=redmine.issue-20449.20240423194409.10206@ruby-lang.org \
    --to=ruby-core@ruby-lang.org \
    --cc=noreply@ruby-lang.org \
    --cc=ruby-core@ml.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 read-only IMAP folder(s) and NNTP newsgroup(s).