ruby-core@ruby-lang.org archive (unofficial mirror)
 help / color / mirror / Atom feed
From: SASADA Koichi <ko1@atdot.net>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:72436] Re: Ruby 2.3.0-preview2 Released
Date: Tue, 22 Dec 2015 22:53:19 +0900	[thread overview]
Message-ID: <567955CF.8080602@atdot.net> (raw)
In-Reply-To: <20151211090624.GA30536@dcvr.yhbt.net>

On 2015/12/11 18:06, Eric Wong wrote:
> SASADA Koichi <ko1@atdot.net> wrote:
>> Please add your optimizations before RC1.
>> (maybe Eric Wong wants to add)
> 
> Most I've done are pretty minor or for rarely-used corner case.
> Not sure which are really worth mentioning and public ones are
> already in NEWS.

Sorry, I missed your post.

Maybe you can add entries which you *WANT* to add :)
Can you write sentences for particular topics?
(you are absolutely better English writer than me)

> 
> * compile optimized case dispatch for all special constant literals
>   (Aaron Patterson)
>   https://bugs.ruby-lang.org/issues/11769
> 
> * Fiddle::Function#call releases the GVL
>   https://bugs.ruby-lang.org/issues/11607
>   (Just added to NEWS)
> 
> * All non-blocking IO and socket methods allow `exception: false'
>   https://bugs.ruby-lang.org/issues/10532
>   https://bugs.ruby-lang.org/issues/11229
>   ...and reduced calling overhead of these methods:
>   https://bugs.ruby-lang.org/issues/11339
>   (Already in NEWS)
> 
> * Socket#recv* methods allow a destination buffer to reduce GC pressure
>   https://bugs.ruby-lang.org/issues/11242
>   (Already in NEWS)
> 
> * stdlib updated to use exception-free non-blocking I/O
>   https://bugs.ruby-lang.org/issues/11044
> 
> * (Linux-only) waiting on a single FD anywhere in the stdlib no longer
>   uses select(2), making it immune to slowdowns with high-numbered FDs
>   https://bugs.ruby-lang.org/issues/11081
>   https://bugs.ruby-lang.org/issues/11377
> 
> * speedup big structs (Yura Sokolov)
>   https://bugs.ruby-lang.org/issues/10585
> 
> * memory reductions for instance variables in non-pure-Ruby classes
>   (T_DATA, T_FILE, etc...)
>   https://bugs.ruby-lang.org/issues/11170
> 
> * speed up Set#include?  (Ismael Abreu)
>   https://bugs.ruby-lang.org/issues/10754
> 
> Improvements by a thousand cuts, maybe :)
> 



-- 
// SASADA Koichi at atdot dot net

  reply	other threads:[~2015-12-22 13:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-11  1:40 [ruby-core:72045] Ruby 2.3.0-preview2 Released NARUSE, Yui
2015-12-11  1:48 ` [ruby-core:72047] " SASADA Koichi
2015-12-11  9:06   ` [ruby-core:72054] " Eric Wong
2015-12-22 13:53     ` SASADA Koichi [this message]
2015-12-22 20:05       ` [ruby-core:72440] " Eric Wong
2015-12-23  1:47         ` [ruby-core:72448] " SASADA Koichi
2015-12-23  3:12           ` [ruby-core:72450] " Eric Wong
2015-12-24  7:16             ` [ruby-core:72467] " SASADA Koichi
2015-12-24  8:52               ` [ruby-core:72468] " Eric Wong
2015-12-18  4:13 ` [ruby-core:72336] " Joseph Jones

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=567955CF.8080602@atdot.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).