1
0
Fork 0
mirror of https://github.com/ruby/ruby.git synced 2022-11-09 12:17:21 -05:00
ruby--ruby/NEWS.md

171 lines
5.1 KiB
Markdown
Raw Normal View History

# NEWS for Ruby 2.8.0 (tentative; to be 3.0.0)
2020-02-16 15:00:34 -05:00
This document is a list of user visible feature changes
since the **2.7.0** release, 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. `https://bugs.ruby-lang.org/issues/$FEATURE_OR_BUG_NUMBER`).
## Language changes
2020-02-28 19:12:13 -05:00
* Keyword arguments are now separated from positional arguments.
Code that resulted in deprecation warnings in Ruby 2.7 will now
result in ArgumentError or different behavior. [[Feature #14183]]
* Procs accepting a single rest argument and keywords are no longer
subject to autosplatting. This now matches the behavior of Procs
accepting a single rest argument and no keywords.
[[Feature #16166]]
```ruby
pr = proc{|*a, **kw| [a, kw]}
pr.call([1])
# 2.7 => [[1], {}]
# 3.0 => [[[1]], {}]
pr.call([1, {a: 1}])
# 2.7 => [[1], {:a=>1}] # and deprecation warning
# 3.0 => [[[1, {:a=>1}]], {}]
```
2020-02-16 15:00:49 -05:00
* $SAFE is now a normal global variable with no special behavior.
[[Feature #16131]]
2020-02-28 19:12:13 -05:00
* yield in singleton class definitions in methods is now a SyntaxError
instead of a warning. yield in a class definition outside of a method
is now a SyntaxError instead of a LocalJumpError. [[Feature #15575]]
## Command line options
## Core classes updates
Outstanding ones only.
* Dir
* Modified method
* Dir.glob and Dir.[] now sort the results by default, and
accept `sort:` keyword option. [[Feature #8709]]
* Hash
* Modified method
* Hash#transform_keys now accepts a hash that maps keys to new
keys. [[Feature #16274]]
2020-02-28 19:12:13 -05:00
* Kernel
* Modified method
2020-02-28 23:24:29 -05:00
* Kernel#clone when called with `freeze: false` keyword will call
#initialize_clone with the `freeze: false` keyword.
2020-02-28 19:12:13 -05:00
[[Bug #14266]]
* Kernel#eval when called with two arguments will use "(eval)"
2020-02-28 23:24:29 -05:00
for `__FILE__` and 1 for `__LINE__` in the evaluated code.
2020-02-28 19:12:13 -05:00
[[Bug #4352]]
* Module
* Modified method
* Module#include now includes the arguments in modules and
classes that have already included or prepended the receiver,
mirroring the behavior if the arguments were included in the
receiver before the other modules and classes included or
prepended the receiver. [[Feature #9573]]
* Symbol
* Modified method
* Symbol#to_proc now returns a lambda Proc.
[[Feature #16260]]
## Stdlib updates
Outstanding ones only.
* Net::HTTP
* New method
* Add Net::HTTP#verify_hostname= and Net::HTTP#verify_hostname
2020-02-16 15:00:49 -05:00
to skip hostname verification. [[Feature #16555]]
* Modified method
* Net::HTTP.get, Net::HTTP.get_response, and Net::HTTP.get_print can
take request headers as a Hash in the second argument when the first
argument is a URI.
## Compatibility issues
Excluding feature bug fixes.
* Regexp literals are frozen [[Feature #8948]] [[Feature #16377]]
```ruby
/foo/.frozen? #=> true
```
* Bundled gems
* net-telnet and xmlrpc have been removed from the bundled gems.
If you are interested in maintaining them, please comment on
your plan to https://github.com/ruby/xmlrpc
or https://github.com/ruby/net-telnet.
* EXPERIMENTAL: Hash#each consistently yields a 2-element array [[Bug #12706]]
* Now `{ a: 1 }.each(&->(k, v) { })` raises an ArgumentError
due to lambda's arity check.
* This is experimental; if it brings a big incompatibility issue,
it may be reverted until 2.8/3.0 release.
## Stdlib compatibility issues
Excluding feature bug fixes.
## C API updates
2020-02-28 19:12:13 -05:00
* C API functions related to $SAFE have been removed.
[[Feature #16131]]
## Implementation improvements
Reduce allocations for keyword argument hashes Previously, passing a keyword splat to a method always allocated a hash on the caller side, and accepting arbitrary keywords in a method allocated a separate hash on the callee side. Passing explicit keywords to a method that accepted a keyword splat did not allocate a hash on the caller side, but resulted in two hashes allocated on the callee side. This commit makes passing a single keyword splat to a method not allocate a hash on the caller side. Passing multiple keyword splats or a mix of explicit keywords and a keyword splat still generates a hash on the caller side. On the callee side, if arbitrary keywords are not accepted, it does not allocate a hash. If arbitrary keywords are accepted, it will allocate a hash, but this commit uses a callinfo flag to indicate whether the caller already allocated a hash, and if so, the callee can use the passed hash without duplicating it. So this commit should make it so that a maximum of a single hash is allocated during method calls. To set the callinfo flag appropriately, method call argument compilation checks if only a single keyword splat is given. If only one keyword splat is given, the VM_CALL_KW_SPLAT_MUT callinfo flag is not set, since in that case the keyword splat is passed directly and not mutable. If more than one splat is used, a new hash needs to be generated on the caller side, and in that case the callinfo flag is set, indicating the keyword splat is mutable by the callee. In compile_hash, used for both hash and keyword argument compilation, if compiling keyword arguments and only a single keyword splat is used, pass the argument directly. On the caller side, in vm_args.c, the callinfo flag needs to be recognized and handled. Because the keyword splat argument may not be a hash, it needs to be converted to a hash first if not. Then, unless the callinfo flag is set, the hash needs to be duplicated. The temporary copy of the callinfo flag, kw_flag, is updated if a hash was duplicated, to prevent the need to duplicate it again. If we are converting to a hash or duplicating a hash, we need to update the argument array, which can including duplicating the positional splat array if one was passed. CALLER_SETUP_ARG and a couple other places needs to be modified to handle similar issues for other types of calls. This includes fairly comprehensive tests for different ways keywords are handled internally, checking that you get equal results but that keyword splats on the caller side result in distinct objects for keyword rest parameters. Included are benchmarks for keyword argument calls. Brief results when compiled without optimization: def kw(a: 1) a end def kws(**kw) kw end h = {a: 1} kw(a: 1) # about same kw(**h) # 2.37x faster kws(a: 1) # 1.30x faster kws(**h) # 2.19x faster kw(a: 1, **h) # 1.03x slower kw(**h, **h) # about same kws(a: 1, **h) # 1.16x faster kws(**h, **h) # 1.14x faster
2020-02-24 15:05:07 -05:00
* The number of hashes allocated when using a keyword splat in
a method call has been reduced to a maximum of 1, and passing
a keyword splat to a method that accepts specific keywords
does not allocate a hash.
## Miscellaneous changes
2020-02-28 23:24:29 -05:00
* Methods using `ruby2_keywords` will no longer keep empty keyword
2020-02-28 19:12:13 -05:00
splats, those are now removed just as they are for methods not
2020-02-28 23:24:29 -05:00
using `ruby2_keywords`.
2020-02-28 19:12:13 -05:00
* Taint deprecation warnings are now issued in regular mode in
addition to verbose warning mode. [[Feature #16131]]
2020-02-28 22:20:49 -05:00
[Bug #4352]: https://bugs.ruby-lang.org/issues/4352
[Feature #8709]: https://bugs.ruby-lang.org/issues/8709
[Feature #8948]: https://bugs.ruby-lang.org/issues/8948
2020-02-28 22:20:49 -05:00
[Feature #9573]: https://bugs.ruby-lang.org/issues/9573
[Feature #14183]: https://bugs.ruby-lang.org/issues/14183
[Bug #14266]: https://bugs.ruby-lang.org/issues/14266
2020-02-16 15:00:49 -05:00
[Feature #15575]: https://bugs.ruby-lang.org/issues/15575
[Feature #16131]: https://bugs.ruby-lang.org/issues/16131
2020-03-09 23:43:49 -04:00
[Feature #16166]: https://bugs.ruby-lang.org/issues/16166
[Feature #16260]: https://bugs.ruby-lang.org/issues/16260
[Feature #16274]: https://bugs.ruby-lang.org/issues/16274
[Feature #16377]: https://bugs.ruby-lang.org/issues/16377
2020-03-18 00:57:03 -04:00
[Bug #12706]: https://bugs.ruby-lang.org/issues/12706
2020-02-16 15:00:49 -05:00
[Feature #16555]: https://bugs.ruby-lang.org/issues/16555