2022-12-26 05:42:36 +03:00
# NEWS for Ruby 3.3.0
2020-01-15 06:42:47 +03:00
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.
2020-01-15 06:42:47 +03:00
2020-12-22 22:27:38 +03:00
Note that each entry is kept to a minimum, see links for details.
2020-01-15 06:42:47 +03:00
2020-01-18 11:46:52 +03:00
## 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
2023-04-14 12:26:09 +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 ]]
2020-03-03 11:37:51 +03:00
## Core classes updates
2021-12-15 19:24:31 +03:00
Note: We're only listing outstanding class updates.
2020-01-15 06:42:47 +03:00
2023-01-05 20:41:57 +03:00
* Array
* `Array#pack` now raises ArgumentError for unknown directives. [[Bug #19150 ]]
2023-01-17 00:29:43 +03:00
* Dir
2023-02-10 00:34:37 +03:00
* `Dir.for_fd` added for returning a Dir object for the directory specified
by the provided directory file descriptor. [[Feature #19347 ]]
2023-01-17 00:29:43 +03:00
* `Dir.fchdir` added for changing the directory to the directory specified
by the provided directory file descriptor. [[Feature #19347 ]]
2023-02-09 23:45:52 +03:00
* `Dir#chdir` added for changing the directory to the directory specified
by the provided `Dir` object. [[Feature #19347 ]]
2023-01-17 00:29:43 +03:00
2023-04-19 02:19:31 +03:00
* MatchData
* MatchData#named_captures now accepts optional `symbolize_names` keyword. [[Feature #19591 ]]
2023-01-05 20:41:57 +03:00
* String
* `String#unpack` now raises ArgumentError for unknown directives. [[Bug #19150 ]]
2023-01-20 15:40:25 +03:00
* `String#bytesplice` now accepts new arguments index/length or range of the source string to be copied. [[Feature #19314 ]]
2023-01-05 20:41:57 +03:00
2022-02-18 14:54:42 +03:00
* 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 ]]
2023-06-21 10:49:51 +03:00
* Module
* `Module#set_temporary_name` added for setting a temporary name for a module. [[Feature #19521 ]]
2020-03-03 11:37:51 +03:00
## Stdlib updates
2023-01-10 18:58:12 +03:00
The following default gems are updated.
2022-11-26 06:53:10 +03:00
2023-01-10 18:58:12 +03:00
* RubyGems 3.5.0.dev
2023-02-21 18:36:48 +03:00
* bigdecimal 3.1.4
2023-01-10 18:58:12 +03:00
* bundler 2.5.0.dev
2023-06-28 10:53:31 +03:00
* csv 3.2.8
2023-01-10 18:58:12 +03:00
* fiddle 1.1.2
2023-04-03 08:20:16 +03:00
* fileutils 1.7.1
2023-07-13 05:16:53 +03:00
* irb 1.7.3
2023-05-25 12:12:20 +03:00
* nkf 0.1.3
2023-01-10 18:58:12 +03:00
* optparse 0.4.0.pre.1
2023-02-07 15:27:05 +03:00
* psych 5.1.0
2023-07-08 11:54:34 +03:00
* reline 0.3.6
2023-06-02 11:21:30 +03:00
* stringio 3.0.8
2023-02-21 14:00:14 +03:00
* strscan 3.0.7
2023-05-23 04:24:57 +03:00
* syntax_suggest 1.1.0
2023-04-13 12:52:07 +03:00
* time 0.2.2
2023-06-23 06:52:44 +03:00
* timeout 0.4.0
2023-06-29 04:08:30 +03:00
* uri 0.12.2
2023-01-03 11:15:28 +03:00
2023-01-10 18:58:12 +03:00
The following bundled gems are updated.
2022-11-26 06:53:10 +03:00
2023-06-17 09:59:21 +03:00
* minitest 5.18.1
2023-06-25 10:00:17 +03:00
* test-unit 3.6.1
2023-06-13 09:59:40 +03:00
* net-imap 0.3.6
2023-04-28 05:05:08 +03:00
* rbs 3.1.0
2023-03-06 09:04:03 +03:00
* typeprof 0.21.7
2023-05-09 06:57:54 +03:00
* debug 1.8.0
2023-01-03 11:15:28 +03:00
2023-06-09 09:47:23 +03:00
The following default gem is now bundled.
2023-06-14 08:25:02 +03:00
* racc 1.7.1
2023-06-09 09:47:23 +03:00
2023-01-10 18:58:12 +03:00
See GitHub releases like [Logger ](https://github.com/ruby/logger/releases ) or
changelog for details of the default gems or bundled gems.
2022-12-22 06:25:00 +03:00
2022-12-15 20:20:59 +03:00
## Supported platforms
2020-03-03 11:37:51 +03:00
## Compatibility issues
2020-08-24 09:38:03 +03:00
## Stdlib compatibility issues
2020-06-18 15:11:19 +03:00
2023-06-09 10:30:50 +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
2020-01-18 11:46:52 +03:00
## C API updates
2020-01-15 06:42:47 +03:00
2020-01-18 11:46:52 +03:00
## Implementation improvements
2020-01-15 06:42:47 +03:00
2023-05-05 01:52:59 +03:00
* `defined?(@ivar)` is optimized with Object Shapes.
### YJIT
2023-05-05 01:58:49 +03:00
* Significant performance improvements over 3.2
* Splat and rest arguments support has been improved.
* Registers are allocated for stack operations of the virtual machine.
* More calls with optional arguments are compiled.
* `Integer#!=` , `String#!=` , `Kernel#block_given?` , `Kernel#is_a?` ,
`Kernel#instance_of?` , `Module#===` are specially optimized.
* Instance variables no longer exit to the interpreter
with megamorphic Object Shapes.
2023-05-05 01:52:59 +03:00
* Metadata for compiled code uses a lot less memory.
2023-05-05 01:58:49 +03:00
* Improved code generation on ARM64
* Option to start YJIT in paused mode and then later enable it manually
* `--yjit-pause` and `RubyVM::YJIT.resume`
* This can be used to enable YJIT only once your application is done booting
* Exit tracing option now supports sampling
* `--trace-exits-sample-rate=N`
2023-07-06 00:42:20 +03:00
* The default value for `--yjit-exec-mem-size` is changed from 64 to 128.
2023-05-05 01:58:49 +03:00
* Multiple bug fixes
2023-01-05 20:41:57 +03:00
2023-05-05 02:10:14 +03:00
### RJIT
* Introduced a pure-Ruby JIT compiler RJIT and replaced MJIT.
* 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.
2023-04-14 12:26:09 +03:00
[Feature #18498 ]: https://bugs.ruby-lang.org/issues/18498
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
2023-01-17 00:29:43 +03:00
[Feature #19347 ]: https://bugs.ruby-lang.org/issues/19347
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
