ruby/NEWS.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

202 строки
7.0 KiB
Markdown
Исходник Обычный вид История

2022-12-26 05:42:36 +03:00
# NEWS for Ruby 3.3.0
2021-12-15 19:24:31 +03:00
This document is a list of user-visible feature changes
2022-12-26 05:42:36 +03:00
since the **3.2.0** release, except for bug fixes.
Note that each entry is kept to a minimum, see links for details.
## Language changes
Evaluate multiple assignment left hand side before right hand side In regular assignment, Ruby evaluates the left hand side before the right hand side. For example: ```ruby foo[0] = bar ``` Calls `foo`, then `bar`, then `[]=` on the result of `foo`. Previously, multiple assignment didn't work this way. If you did: ```ruby abc.def, foo[0] = bar, baz ``` Ruby would previously call `bar`, then `baz`, then `abc`, then `def=` on the result of `abc`, then `foo`, then `[]=` on the result of `foo`. This change makes multiple assignment similar to single assignment, changing the evaluation order of the above multiple assignment code to calling `abc`, then `foo`, then `bar`, then `baz`, then `def=` on the result of `abc`, then `[]=` on the result of `foo`. Implementing this is challenging with the stack-based virtual machine. We need to keep track of all of the left hand side attribute setter receivers and setter arguments, and then keep track of the stack level while handling the assignment processing, so we can issue the appropriate topn instructions to get the receiver. Here's an example of how the multiple assignment is executed, showing the stack and instructions: ``` self # putself abc # send abc, self # putself abc, foo # send abc, foo, 0 # putobject 0 abc, foo, 0, [bar, baz] # evaluate RHS abc, foo, 0, [bar, baz], baz, bar # expandarray abc, foo, 0, [bar, baz], baz, bar, abc # topn 5 abc, foo, 0, [bar, baz], baz, abc, bar # swap abc, foo, 0, [bar, baz], baz, def= # send abc, foo, 0, [bar, baz], baz # pop abc, foo, 0, [bar, baz], baz, foo # topn 3 abc, foo, 0, [bar, baz], baz, foo, 0 # topn 3 abc, foo, 0, [bar, baz], baz, foo, 0, baz # topn 2 abc, foo, 0, [bar, baz], baz, []= # send abc, foo, 0, [bar, baz], baz # pop abc, foo, 0, [bar, baz] # pop [bar, baz], foo, 0, [bar, baz] # setn 3 [bar, baz], foo, 0 # pop [bar, baz], foo # pop [bar, baz] # pop ``` As multiple assignment must deal with splats, post args, and any level of nesting, it gets quite a bit more complex than this in non-trivial cases. To handle this, struct masgn_state is added to keep track of the overall state of the mass assignment, which stores a linked list of struct masgn_attrasgn, one for each assigned attribute. This adds a new optimization that replaces a topn 1/pop instruction combination with a single swap instruction for multiple assignment to non-aref attributes. This new approach isn't compatible with one of the optimizations previously used, in the case where the multiple assignment return value was not needed, there was no lhs splat, and one of the left hand side used an attribute setter. This removes that optimization. Removing the optimization allowed for removing the POP_ELEMENT and adjust_stack functions. This adds a benchmark to measure how much slower multiple assignment is with the correct evaluation order. This benchmark shows: * 4-9% decrease for attribute sets * 14-23% decrease for array member sets * Basically same speed for local variable sets Importantly, it shows no significant difference between the popped (where return value of the multiple assignment is not needed) and !popped (where return value of the multiple assignment is needed) cases for attribute and array member sets. This indicates the previous optimization, which was dropped in the evaluation order fix and only affected the popped case, is not important to performance. Fixes [Bug #4443]
2021-04-21 20:49:19 +03:00
## Command line options
* A new `performance` warning category was introduced.
They are not displayed by default even in verbose mode.
Turn them on with `-W:performance` or `Warning[:performance] = true`. [[Feature #19538]]
2023-08-29 07:52:18 +03:00
* The `RUBY_GC_HEAP_INIT_SLOTS` environment variable has been deprecated and
removed. Environment variables `RUBY_GC_HEAP_%d_INIT_SLOTS` should be
2023-08-29 07:52:18 +03:00
used instead. [[Feature #19785]]
## Core classes updates
2021-12-15 19:24:31 +03:00
Note: We're only listing outstanding class updates.
* Array
2023-08-29 07:52:18 +03:00
* Array#pack now raises ArgumentError for unknown directives. [[Bug #19150]]
* Dir
2023-08-29 07:52:18 +03:00
* Dir.for_fd added for returning a Dir object for the directory specified
by the provided directory file descriptor. [[Feature #19347]]
2023-08-29 07:52:18 +03:00
* Dir.fchdir added for changing the directory to the directory specified
by the provided directory file descriptor. [[Feature #19347]]
2023-08-29 07:52:18 +03:00
* Dir#chdir added for changing the directory to the directory specified by
the provided `Dir` object. [[Feature #19347]]
* MatchData
2023-08-29 07:52:18 +03:00
* MatchData#named_captures now accepts optional `symbolize_names`
keyword. [[Feature #19591]]
* Module
* Module#set_temporary_name added for setting a temporary name for a
module. [[Feature #19521]]
* ObjectSpace::WeakKeyMap
* New core class to build collections with weak references.
The class use equality semantic to lookup keys like a regular hash,
but it doesn't hold strong references on the keys. [[Feature #18498]]
* Process.warmup
* Notify the Ruby virtual machine that the boot sequence is finished,
and that now is a good time to optimize the application. This is useful
for long running applications. The actual optimizations performed are entirely
2023-08-25 04:45:34 +03:00
implementation specific and may change in the future without notice. [[Feature #18885]]
* Process::Status
* Process::Status#& and Process::Status#>> are deprecated. [[Bug #19868]]
* Refinement
* Add Refinement#target as an alternative of Refinement#refined_class.
2023-08-29 07:52:18 +03:00
Refinement#refined_class is deprecated and will be removed in Ruby
3.4. [[Feature #19714]]
* String
* String#unpack now raises ArgumentError for unknown directives. [[Bug #19150]]
* String#bytesplice now accepts new arguments index/length or range of the
source string to be copied. [[Feature #19314]]
## Stdlib updates
* RubyGems and Bundler warn if users require gem that is scheduled to become the bundled gems
in the future version of Ruby. [[Feature #19351]] [[Feature #19776]] [[Feature #19843]]
* Socket#recv and Socket#recv_nonblock returns `nil` instead of an empty string on closed
connections. Socket#recvmsg and Socket#recvmsg_nonblock returns `nil` instead of an empty packet on closed
connections. [[Bug #19012]]
* Random::Formatter#alphanumeric is extended to accept optional `chars`
keyword argument. [[Feature #18183]]
The following default gems are updated.
* RubyGems 3.5.0.dev
* bigdecimal 3.1.5
* bundler 2.5.0.dev
* csv 3.2.8
* erb 4.0.3
* fiddle 1.1.2
* fileutils 1.7.1
* irb 1.8.3
* nkf 0.1.3
* openssl 3.2.0
* optparse 0.4.0.pre.1
* prism 0.15.1
* psych 5.1.1.1
* reline 0.3.9
* stringio 3.0.9
* strscan 3.0.7
* syntax_suggest 1.1.0
* time 0.2.2
* timeout 0.4.0
* uri 0.12.2
The following bundled gems are updated.
2023-09-07 09:59:55 +03:00
* minitest 5.20.0
2023-06-25 10:00:17 +03:00
* test-unit 3.6.1
2023-07-28 09:59:38 +03:00
* rexml 3.2.6
2023-08-12 10:00:20 +03:00
* rss 0.3.0
2023-10-10 10:00:15 +03:00
* net-imap 0.4.1
2023-09-28 05:47:00 +03:00
* net-smtp 0.4.0
* rbs 3.2.2
* typeprof 0.21.8
* debug 1.8.0
The following default gem is now bundled.
* racc 1.7.1
See GitHub releases like [Logger](https://github.com/ruby/logger/releases) or
changelog for details of the default gems or bundled gems.
## Supported platforms
## Compatibility issues
## Stdlib compatibility issues
2020-06-18 15:11:19 +03:00
* `racc` is promoted bundled gems.
* You need to add `racc` to your `Gemfile` if you use `racc` under bundler environment.
* `ext/readline` is retired
* We have `reline` that is pure Ruby implementation compatible with `ext/readline` API. We rely on `reline` in the future. If you need to use `ext/readline`, you can install `ext/readline` via rubygems.org with `gem install readline-ext`.
* We no longer need to install libraries like `libreadline` or `libedit`.
2023-05-10 03:56:54 +03:00
## C API updates
## Implementation improvements
* `defined?(@ivar)` is optimized with Object Shapes.
### YJIT
* Major performance improvements over 3.2
* Support for splat and rest arguments has been improved.
* Registers are allocated for stack operations of the virtual machine.
* More calls with optional arguments are compiled.
* Exception handlers are also compiled.
* Instance variables no longer exit to the interpreter
with megamorphic Object Shapes.
* Unsupported call types no longer exit to the interpreter.
2023-08-29 07:52:18 +03:00
* Integer#!=, String#!=, Kernel#block_given?, Kernel#is_a?,
Kernel#instance_of?, Module#=== are specially optimized.
* Now more than 3x faster than the interpreter on optcarrot!
* Metadata for compiled code uses a lot less memory.
* Generate more compact code on ARM64
* Option to start YJIT in paused mode and then later enable it manually
2023-08-29 07:52:18 +03:00
* `--yjit-pause` and RubyVM::YJIT.resume
* This can be used to enable YJIT only once your application is done booting
2023-10-17 05:30:59 +03:00
* `ratio_in_yjit` stat produced by `--yjit-stats` is now available in release builds,
a special stats or dev build is no longer required.
* Exit tracing option now supports sampling
* `--trace-exits-sample-rate=N`
* `--yjit-stats=quiet` is added to avoid printing stats on exit.
* The default value for `--yjit-exec-mem-size` is changed from 64 to 128.
* More thorough testing and multiple bug fixes
2023-09-20 20:14:55 +03:00
### MJIT
* MJIT is removed.
* `--disable-jit-support` is removed. Consider using `--disable-yjit --disable-rjit` instead.
### RJIT
2023-09-20 20:14:55 +03:00
* Introduced a pure-Ruby JIT compiler RJIT.
* RJIT supports only x86\_64 architecture on Unix platforms.
* Unlike MJIT, it doesn't require a C compiler at runtime.
* RJIT exists only for experimental purposes.
* You should keep using YJIT in production.
[Feature #18183]: https://bugs.ruby-lang.org/issues/18183
[Feature #18498]: https://bugs.ruby-lang.org/issues/18498
[Feature #18885]: https://bugs.ruby-lang.org/issues/18885
2023-09-28 20:32:04 +03:00
[Bug #19012]: https://bugs.ruby-lang.org/issues/19012
2023-04-18 03:28:47 +03:00
[Bug #19150]: https://bugs.ruby-lang.org/issues/19150
2023-01-23 03:34:03 +03:00
[Feature #19314]: https://bugs.ruby-lang.org/issues/19314
[Feature #19347]: https://bugs.ruby-lang.org/issues/19347
[Feature #19351]: https://bugs.ruby-lang.org/issues/19351
2023-07-14 03:01:10 +03:00
[Feature #19521]: https://bugs.ruby-lang.org/issues/19521
2023-04-17 16:34:20 +03:00
[Feature #19538]: https://bugs.ruby-lang.org/issues/19538
2023-05-15 16:35:41 +03:00
[Feature #19591]: https://bugs.ruby-lang.org/issues/19591
2023-08-01 03:27:25 +03:00
[Feature #19714]: https://bugs.ruby-lang.org/issues/19714
[Feature #19776]: https://bugs.ruby-lang.org/issues/19776
[Feature #19785]: https://bugs.ruby-lang.org/issues/19785
[Feature #19843]: https://bugs.ruby-lang.org/issues/19843
[Bug #19868]: https://bugs.ruby-lang.org/issues/19868