ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: "jeremyevans0 (Jeremy Evans) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "jeremyevans0 (Jeremy Evans)" <noreply@ruby-lang.org>
Subject: [ruby-core:111864] [Ruby master Bug#11230] Should rb_struct_s_members() be public API?
Date: Tue, 17 Jan 2023 21:37:40 +0000 (UTC)	[thread overview]
Message-ID: <redmine.journal-101278.20230117213739.772@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-11230.20150606200632.772@ruby-lang.org

Issue #11230 has been updated by jeremyevans0 (Jeremy Evans).


I submitted a pull request to remove the prototype from the public header files: https://github.com/ruby/ruby/pull/7141

`rb_struct_s_members` is still an exported symbol as it is used internally by `marshal.c`.

One of reasons stated to remove this method is that it returns a hidden Array.  However, `rb_struct_members` appears to return the same hidden Array (that method is also used internally by `marshal.c`).  Should we consider removing `rb_struct_members` from the public API as well?

----------------------------------------
Bug #11230: Should rb_struct_s_members() be public API?
https://bugs.ruby-lang.org/issues/11230#change-101278

* Author: Eregon (Benoit Daloze)
* Status: Open
* Priority: Normal
* ruby -v: ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
rb_struct_s_members() is declared in include/ruby/intern.h.

However it seems this is a fairly internal API as it returns an hidden Array.

For instance, there was a try to specify the behavior in
https://github.com/rubinius/rubinius/commit/2642a30c57973987d2a7b7e85b3ce1e78100a31b
but that produces only erratic behavior on MRI because that usage is not intended.

A valid usage might be:

    static VALUE get_struct_member(VALUE self, VALUE obj, VALUE i) {
        return RARRAY_AREF(rb_struct_s_members(obj), NUM2INT(i));
    }

    p get_struct_member(Struct.new(:a, :bb), 1)
    

But do we need such access and is it worth exposing a potentially dangerous function like this?



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

  parent reply	other threads:[~2023-01-17 21:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <redmine.issue-11230.20150606200632.772@ruby-lang.org>
2021-04-17 17:06 ` [ruby-core:103500] [Ruby master Bug#11230] Should rb_struct_s_members() be public API? merch-redmine
2023-01-17 21:37 ` jeremyevans0 (Jeremy Evans) via ruby-core [this message]
2023-02-10  1:36 ` [ruby-core:112318] " mame (Yusuke Endoh) 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.journal-101278.20230117213739.772@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).