2015-12-24 12:25:26 -05:00
|
|
|
# -*- rdoc -*-
|
|
|
|
|
|
|
|
|
|
= NEWS for Ruby 2.4.0
|
|
|
|
|
|
|
|
|
|
This document is a list of user visible feature changes made between
|
|
|
|
|
releases except for bug fixes.
|
|
|
|
|
|
|
|
|
|
Note that each entry is kept so brief that no reason behind or
|
|
|
|
|
reference information is supplied with. For a full list of changes
|
|
|
|
|
with all sufficient information, see the ChangeLog file or Redmine
|
|
|
|
|
(e.g. <tt>https://bugs.ruby-lang.org/issues/$FEATURE_OR_BUG_NUMBER</tt>)
|
|
|
|
|
|
|
|
|
|
== Changes since the 2.3.0 release
|
|
|
|
|
|
|
|
|
|
=== Language changes
|
|
|
|
|
|
2016-04-13 01:36:26 -04:00
|
|
|
* Multiple assignment in conditional expression is now allowed.
|
|
|
|
|
[Feature #10617]
|
|
|
|
|
|
2015-12-24 12:25:26 -05:00
|
|
|
=== Core classes updates (outstanding ones only)
|
|
|
|
|
|
2016-03-17 08:49:19 -04:00
|
|
|
* Array
|
2016-04-14 21:17:51 -04:00
|
|
|
|
2016-03-17 08:49:19 -04:00
|
|
|
* Array#max and Array#min. [Feature #12172]
|
|
|
|
|
This may cause a tiny incompatibility: if you redefine
|
|
|
|
|
Enumerable#max and call max to an Array, your redefinition will be
|
|
|
|
|
now ignored. You should also redefine Array#max.
|
|
|
|
|
|
2016-04-13 10:55:18 -04:00
|
|
|
* Array#sum [Feature #12217]
|
|
|
|
|
|
2016-02-16 03:34:47 -05:00
|
|
|
* Dir
|
|
|
|
|
|
2016-02-16 07:25:54 -05:00
|
|
|
* Dir.empty?. [Feature #10121]
|
2016-02-16 03:34:47 -05:00
|
|
|
|
2016-04-13 02:14:12 -04:00
|
|
|
* File
|
|
|
|
|
|
|
|
|
|
* File.empty?. [Feature #9969]
|
|
|
|
|
|
2016-04-14 21:17:51 -04:00
|
|
|
* Float
|
|
|
|
|
|
|
|
|
|
* Float#ceil and Float#floor now take an optional digits, as well as
|
|
|
|
|
Float#round. [Feature #12245]
|
|
|
|
|
|
|
|
|
|
* Integer
|
|
|
|
|
|
|
|
|
|
* Integer#ceil and Integer#floor now take an optional digits, as well
|
|
|
|
|
as Integer#round. [Feature #12245]
|
|
|
|
|
|
2016-02-16 22:21:35 -05:00
|
|
|
* String
|
|
|
|
|
|
|
|
|
|
* String.new(capacity: size) [Feature #12024]
|
|
|
|
|
|
2016-02-20 23:52:04 -05:00
|
|
|
* Symbol
|
|
|
|
|
|
|
|
|
|
* Symbol#match now returns MatchData. [Bug #11991]
|
|
|
|
|
|
2016-02-18 00:29:18 -05:00
|
|
|
* MatchData
|
|
|
|
|
|
|
|
|
|
* MatchData#named_captures [Feature #11999]
|
|
|
|
|
|
2015-12-24 12:25:26 -05:00
|
|
|
=== Stdlib updates (outstanding ones only)
|
|
|
|
|
|
2016-01-01 08:02:56 -05:00
|
|
|
* CSV
|
2016-04-14 21:17:51 -04:00
|
|
|
|
2016-01-01 08:02:56 -05:00
|
|
|
* Add a liberal_parsing option. [Feature #11839]
|
|
|
|
|
|
2016-01-06 03:23:10 -05:00
|
|
|
* optparse
|
2016-04-14 21:17:51 -04:00
|
|
|
|
2016-01-06 03:23:10 -05:00
|
|
|
* Add an into option. [Feature #11191]
|
|
|
|
|
|
2016-04-15 11:26:48 -04:00
|
|
|
=== Compatibility issues (excluding feature bug fixes)
|
|
|
|
|
|
|
|
|
|
* Array#sum is implemented. Ruby itself has no compatibility problem
|
|
|
|
|
because Ruby didn't have sum method for arrays before Ruby 2.4.
|
|
|
|
|
However many third party gems, activesupport, facets, simple_stats, etc,
|
|
|
|
|
defines sum method. These implementations are mostly compatible but
|
|
|
|
|
there are subtle differences.
|
|
|
|
|
Ruby's sum method should be mostly compatible but it is impossible to
|
|
|
|
|
be perfectly compatible with all of them.
|
2015-12-24 12:25:26 -05:00
|
|
|
|
|
|
|
|
=== C API updates
|
|
|
|
|
|
2016-01-06 21:34:33 -05:00
|
|
|
* ruby_show_version() will no longer exits the process, if
|
|
|
|
|
RUBY_SHOW_COPYRIGHT_TO_DIE is set to 0. This will be the default in
|
|
|
|
|
the future.
|
|
|
|
|
|
2015-12-24 12:25:26 -05:00
|
|
|
=== Supported platform changes
|
|
|
|
|
|
|
|
|
|
=== Implementation improvements
|
2016-03-17 08:49:19 -04:00
|
|
|
|
|
|
|
|
* In some condition, `[x, y].max` and `[x, y].min` are optimized
|
|
|
|
|
so that a temporal array is not created. The concrete condition is
|
|
|
|
|
an implementation detail: currently, the array literal must have no
|
|
|
|
|
splat, must have at least one expression but literal, the length must
|
|
|
|
|
be <= 0x100, and Array#max and min must not be redefined. It will work
|
|
|
|
|
in most casual and real-life use case where it is written with intent
|
|
|
|
|
to `Math.max(x, y)`.
|
