From: Eric Wong <normalperson@yhbt.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:72484] Re: [Ruby trunk - Feature #11614] [Open] [RFC] use id_table for constant tables
Date: Sat, 26 Dec 2015 07:37:26 +0000 [thread overview]
Message-ID: <20151226073726.GA25024@dcvr.yhbt.net> (raw)
In-Reply-To: <20151214111935.GA10268@dcvr.yhbt.net>
Eric Wong <normalperson@yhbt.net> wrote:
> normalperson@yhbt.net wrote:
> > Feature #11614: [RFC] use id_table for constant tables
> > https://bugs.ruby-lang.org/issues/11614
>
> Any comment? I'm pretty sure this was alright,
> but maybe it's 2.4 material. Thanks.
Updated patch on top of latest trunk r53315
http://80x24.org/spew/20151226073256.24943-1-e%4080x24.org/raw
I think I'll commit in a few days since we have a year until 2.4
prev parent reply other threads:[~2015-12-26 7:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-11614.20151022205443@ruby-lang.org>
2015-10-22 20:54 ` [ruby-core:71164] [Ruby trunk - Feature #11614] [Open] [RFC] use id_table for constant tables normalperson
2015-12-14 11:19 ` [ruby-core:72112] " Eric Wong
2015-12-26 7:37 ` Eric Wong [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=20151226073726.GA25024@dcvr.yhbt.net \
--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).