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:117188] [Ruby master Bug#20340] Ractor comments not applying to constant targets
Date: Thu, 14 Mar 2024 19:39:40 +0000 (UTC)	[thread overview]
Message-ID: <redmine.issue-20340.20240314193940.10206@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20340.20240314193940.10206@ruby-lang.org

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

----------------------------------------
Bug #20340: Ractor comments not applying to constant targets
https://bugs.ruby-lang.org/issues/20340

* Author: kddnewton (Kevin Newton)
* Status: Open
* Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
In this example:

```ruby
C, = { foo: bar }
```

You get:

```
== disasm: #<ISeq:<main>@test.rb:1 (1,0)-(1,17)>
0000 putobject                              :foo                      (   1)[Li]
0002 putself
0003 opt_send_without_block                 <calldata!mid:bar, argc:0, FCALL|VCALL|ARGS_SIMPLE>
0005 newhash                                2
0007 dup
0008 expandarray                            1, 0
0011 putspecialobject                       3
0013 setconstant                            :C
0015 leave
```

But there's no difference from:

```ruby
# shareable_constant_value: literal
C, = { foo: bar }
```

I would have expected:

```
== disasm: #<ISeq:<main>@test.rb:1 (1,0)-(2,16)>
0000 putobject                              RubyVM::FrozenCore        (   2)[Li]
0002 putobject                              :foo
0004 putobject                              RubyVM::FrozenCore
0006 putself
0007 opt_send_without_block                 <calldata!mid:bar, argc:0, FCALL|VCALL|ARGS_SIMPLE>
0009 putobject                              "C"
0011 opt_send_without_block                 <calldata!mid:ensure_shareable, argc:2, ARGS_SIMPLE>
0013 newhash                                2
0015 opt_send_without_block                 <calldata!mid:make_shareable, argc:1, ARGS_SIMPLE>
0017 dup
0018 expandarray                            1, 0
0021 putspecialobject                       3
0023 setconstant                            :C
0025 leave
```

Is this omission intentional? For context, I'm building this in prism and I need to know if I should explicitly disable this behavior. 



-- 
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-03-14 19:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-14 19:39 kddnewton (Kevin Newton) via ruby-core [this message]
2024-04-16  6:33 ` [ruby-core:117525] [Ruby master Bug#20340] Ractor comments not applying to constant targets ko1 (Koichi Sasada) 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-20340.20240314193940.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).