From: nobu@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:96774] [Ruby master Bug#16480] Ruby 2.7, C++, and rb_define_method compilation error
Date: Sat, 11 Jan 2020 01:58:50 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-83768.20200111015850.259164c13861cc64@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-16480.20200104180721@ruby-lang.org
Issue #16480 has been updated by nobu (Nobuyoshi Nakada).
Status changed from Assigned to Closed
The arities must be eventually compile-time constants for the nature.
I think this case is quite special, and it is resolved in that project.
----------------------------------------
Bug #16480: Ruby 2.7, C++, and rb_define_method compilation error
https://bugs.ruby-lang.org/issues/16480#change-83768
* Author: jasonroelofs (Jason Roelofs)
* Status: Closed
* Priority: Normal
* Assignee: nobu (Nobuyoshi Nakada)
* Target version:
* ruby -v: ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-darwin18]
* Backport: 2.5: UNKNOWN, 2.6: UNKNOWN
----------------------------------------
I maintain the Rice library which provides constructs for exposing C++ libraries into Ruby. With Ruby 2.7.0 I've got a hard compilation failure that I'm not sure how to fix.[1]
Diving into this, I've found that rb_define_method, when compiled under C++, is now a macro that uses templates to choose the correct overload by the given arity. However, this seems to require a constexpr-compatible use of rb_define_method, making the API unavailable for more dynamic uses[1].
The PR that made these changes is here[3].
I've looked for ways to get around this macro change but have been unable to make anything work. Is there a way I've missed to directly call the underlying C API function or is this now simply not possible with Ruby 2.7.0?
[1] https://github.com/jasonroelofs/rice/issues/119
[2] https://github.com/jasonroelofs/rice/blob/master/rice/detail/method_data.cpp#L78
[3] https://github.com/ruby/ruby/pull/2461
--
https://bugs.ruby-lang.org/
prev parent reply other threads:[~2020-01-11 1:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-16480.20200104180721@ruby-lang.org>
2020-01-04 18:07 ` [ruby-core:96656] [Ruby master Bug#16480] Ruby 2.7, C++, and rb_define_method compilation error ruby
2020-01-06 1:03 ` [ruby-core:96677] " shyouhei
2020-01-09 14:14 ` [ruby-core:96739] " nobu
2020-01-09 23:35 ` [ruby-core:96744] " ruby
2020-01-11 1:58 ` nobu [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-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-83768.20200111015850.259164c13861cc64@ruby-lang.org \
--to=ruby-core@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).