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

594 lines
18 KiB
Markdown
Raw Normal View History

Copy NEWS.md to doc/NEWS-3.0.0.md and update for 3.1.0
2020-12-25 03:31:48 -05:00
# NEWS for Ruby 3.1.0
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
This document is a list of user-visible feature changes
Copy NEWS.md to doc/NEWS-3.0.0.md and update for 3.1.0
2020-12-25 03:31:48 -05:00
since the **3.0.0** release, except for bug fixes.
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
NEWS: We have links now, and there is no changelog anymore [doc]
2020-12-22 14:27:38 -05:00
Note that each entry is kept to a minimum, see links for details.
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
NEWS.md: reduce headings level [ci skip] As the only h2 did not have its exclusively owned body text, merged it to the first paragraph. Then pulled up h3 and deeper headings.
2020-01-18 03:46:52 -05: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 13:49:19 -04:00
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
* The block argument can now be anonymous if the block will
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
only be passed to another method. [[Feature #11256]]
Anonymous block forwarding allows a method to forward a passed block to another method without having to provide a name for the block parameter. Implements [Feature #11256] Co-authored-by: Yusuke Endoh mame@ruby-lang.org Co-authored-by: Nobuyoshi Nakada nobu@ruby-lang.org
2021-11-18 15:44:19 -05:00
```ruby
def foo(&)
bar(&)
end
```
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* Pin operator now takes an expression. [[Feature #17411]]
Pattern matching pin operator against expression [Feature #17411] This commit is based on the patch by @nobu.
2021-03-21 02:12:54 -04:00
```ruby
Prime.each_cons(2).lazy.find_all{_1 in [n, ^(n + 2)]}.take(3).to_a
#=> [[3, 5], [5, 7], [11, 13]]
```
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* Pin operator now supports instance, class, and global variables.
[[Feature #17724]]
Add pattern matching pin support for instance/class/global variables Pin matching for local variables and constants is already supported, and it is fairly simple to add support for these variable types. Note that pin matching for method calls is still not supported without wrapping in parentheses (pin expressions). I think that's for the best as method calls are far more complex (arguments/blocks). Implements [Feature #17724]
2021-05-13 18:31:46 -04:00
Added code fence to the example in [Feature #17724] [ci skip]
2021-07-15 22:23:36 -04:00
```ruby
Add pattern matching pin support for instance/class/global variables Pin matching for local variables and constants is already supported, and it is fairly simple to add support for these variable types. Note that pin matching for method calls is still not supported without wrapping in parentheses (pin expressions). I think that's for the best as method calls are far more complex (arguments/blocks). Implements [Feature #17724]
2021-05-13 18:31:46 -04:00
@n = 5
Prime.each_cons(2).lazy.find{_1 in [n, ^@n]}
#=> [3, 5]
Added code fence to the example in [Feature #17724] [ci skip]
2021-07-15 22:23:36 -04:00
```
Add pattern matching pin support for instance/class/global variables Pin matching for local variables and constants is already supported, and it is fairly simple to add support for these variable types. Note that pin matching for method calls is still not supported without wrapping in parentheses (pin expressions). I think that's for the best as method calls are far more complex (arguments/blocks). Implements [Feature #17724]
2021-05-13 18:31:46 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* One-line pattern matching is no longer experimental.
One-line pattern matching is no longer experimental https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20210715Japan.md#feature-17724-make-the-pin-operator-support-instanceclassglobal-variables-jeremyevans0
2021-07-16 22:13:52 -04:00
Add news about allowing omission of parentheses in one-line pattern matching
2021-12-19 07:37:08 -05:00
* Parentheses can be omitted in one-line pattern matching.
[[Feature #16182]]
```ruby
[0, 1] => _, x
{y: 2} => y:
x #=> 1
y #=> 2
```
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* Multiple assignment evaluation order has been made consistent with
single assignment evaluation order. With single assignment, Ruby
uses a left-to-right evaluation order. With this code:
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 13:49:19 -04:00
```ruby
foo[0] = bar
```
[DOC] Fixed indents in NEWS.md [ci skip]
2021-09-11 06:18:22 -04:00
The following evaluation order is used:
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 13:49:19 -04:00
[DOC] Fixed indents in NEWS.md [ci skip]
2021-09-11 06:18:22 -04:00
1. `foo`
2. `bar`
3. `[]=` called on the result of `foo`
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 13:49:19 -04:00
[DOC] Fixed indents in NEWS.md [ci skip]
2021-09-11 06:18:22 -04:00
In Ruby before 3.1.0, multiple assignment did not follow this
evaluation order. With this code:
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 13:49:19 -04:00
Fix wrong indentation in NEWS.md [ci skip]
2021-12-05 03:15:45 -05:00
```ruby
foo[0], bar.baz = a, b
```
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 13:49:19 -04:00
[DOC] Fixed indents in NEWS.md [ci skip]
2021-09-11 06:18:22 -04:00
Versions of Ruby before 3.1.0 would evaluate in the following
order
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 13:49:19 -04:00
[DOC] Fixed indents in NEWS.md [ci skip]
2021-09-11 06:18:22 -04:00
1. `a`
2. `b`
3. `foo`
4. `[]=` called on the result of `foo`
5. `bar`
6. `baz=` called on the result of `bar`
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 13:49:19 -04:00
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
Starting in Ruby 3.1.0, the evaluation order is now consistent with
single assignment, with the left-hand side being evaluated before
the right-hand side:
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 13:49:19 -04:00
[DOC] Fixed indents in NEWS.md [ci skip]
2021-09-11 06:18:22 -04:00
1. `foo`
2. `bar`
3. `a`
4. `b`
5. `[]=` called on the result of `foo`
6. `baz=` called on the result of `bar`
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 13:49:19 -04:00
[DOC] Fixed indents in NEWS.md [ci skip]
2021-09-11 06:18:22 -04:00
[[Bug #4443]]
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 13:49:19 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* Values in Hash literals and keyword arguments can be omitted.
[[Feature #14579]]
Add a newline [ci skip]
2021-09-16 04:31:39 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
For example,
[DOC] NEWS for [Feature #14579] [ci skip]
2021-09-11 06:13:53 -04:00
Add details of Hash value ommission [ci skip]
2021-09-16 04:28:31 -04:00
* `{x:, y:}` is a syntax sugar of `{x: x, y: y}`.
* `foo(x:, y:)` is a syntax sugar of `foo(x: x, y: y)`.
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
Constant names, local variable names, and method names are allowed as
key names. Note that a reserved word is considered as a local
variable or method name even if it's a pseudo variable name such as
`self`.
[DOC] NEWS for [Feature #14579] [ci skip]
2021-09-11 06:13:53 -04:00
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
* Non main-Ractors can get instance variables (ivars) of classes/modules
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
if ivars refer to shareable objects.
[[Feature #17592]]
update NEWS about last commits.
2021-10-22 12:38:05 -04:00
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
* A command syntax is allowed in endless method definitions, i.e.,
NEWS.md: `def foo = puts "Hello"` is now allowed [Feature #17398]
2021-12-13 00:01:40 -05:00
you can now write `def foo = puts "Hello"`.
Note that `private def foo = puts "Hello"` does not parse.
[[Feature #17398]]
NEWS.md: reduce headings level [ci skip] As the only h2 did not have its exclusively owned body text, merged it to the first paragraph. Then pulled up h3 and deeper headings.
2020-01-18 03:46:52 -05:00
## Command line options
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
NEWS.md: `--disable-gems` is now just for debugging. [Feature #17684]
2021-12-13 00:19:21 -05:00
* `--disable-gems` is now explicitly declared as "just for debugging".
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
Never use it in any real-world codebase.
NEWS.md: `--disable-gems` is now just for debugging. [Feature #17684]
2021-12-13 00:19:21 -05:00
[[Feature #17684]]
[DOC] Separated parenthesized notes from subsection headings As the headings become link anchors, remove less useful notes. [ci skip]
2020-03-03 03:37:51 -05:00
## Core classes updates
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
Note: We're only listing outstanding class updates.
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
NEWS for [Feature #15198] [ci skip]
2021-04-16 03:12:10 -04:00
* Array
* Array#intersect? is added. [[Feature #15198]]
Add Class#descendants Doesn't include receiver or singleton classes. Implements [Feature #14394] Co-authored-by: fatkodima <fatkodima123@gmail.com> Co-authored-by: Benoit Daloze <eregontp@gmail.com>
2021-10-26 15:35:21 -04:00
* Class
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Class#subclasses, which returns an array of classes
directly inheriting from the receiver, not
including singleton classes.
[[Feature #18273]]
```ruby
class A; end
class B < A; end
class C < B; end
class D < A; end
A.subclasses #=> [D, B]
B.subclasses #=> [C]
C.subclasses #=> []
```
Add Class#subclasses Implements [Feature #18273] Returns an array containing the receiver's direct subclasses without singleton classes.
2021-10-28 08:07:11 -04:00
NEWS: [Feature #17312] [ci skip]
2021-01-02 02:42:45 -05:00
* Enumerable
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Enumerable#compact is added. [[Feature #17312]]
NEWS: [Feature #17312] [ci skip]
2021-01-02 02:42:45 -05:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Enumerable#tally now accepts an optional hash to count. [[Feature #17744]]
Enumerable#tally with the resulting hash [Feature #17744]
2021-03-26 03:29:21 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Enumerable#each_cons and each_slice to return a receiver. [[GH-1509]]
Add changes Enumerable#each_cons and each_slice in NEWS [ci skip]
2021-10-28 05:21:27 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
```ruby
[1, 2, 3].each_cons(2){}
# 3.0 => nil
# 3.1 => [1, 2, 3]
Add changes Enumerable#each_cons and each_slice in NEWS [ci skip]
2021-10-28 05:21:27 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
[1, 2, 3].each_slice(2){}
# 3.0 => nil
# 3.1 => [1, 2, 3]
```
Add changes Enumerable#each_cons and each_slice in NEWS [ci skip]
2021-10-28 05:21:27 -04:00
NEWS: [Feature #17312] [ci skip]
2021-01-02 02:42:45 -05:00
* Enumerator::Lazy
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Enumerator::Lazy#compact is added. [[Feature #17312]]
NEWS: [Feature #17312] [ci skip]
2021-01-02 02:42:45 -05:00
NEWS of [Feature #12194] [ci skip]
2021-03-15 07:05:03 -04:00
* File
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* File.dirname now accepts an optional argument for the level to
strip path components. [[Feature #12194]]
NEWS of [Feature #12194] [ci skip]
2021-03-15 07:05:03 -04:00
add a NEWS entry about GC.total_time
2021-12-06 03:36:01 -05:00
* GC
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* "GC.measure_total_time = true" enables the measurement of GC.
Measurement can introduce overhead. It is enabled by default.
GC.measure_total_time returns the current setting.
GC.stat[:time] or GC.stat(:time) returns measured time
Fix a typo [ci skip]
2021-12-17 08:30:23 -05:00
in milli-seconds.
add a NEWS entry about GC.total_time
2021-12-06 03:36:01 -05:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* GC.total_time returns measured time in nano-seconds.
add a NEWS entry about GC.total_time
2021-12-06 03:36:01 -05:00
Add Integer.try_convert [Feature #15211]
2018-10-07 00:02:46 -04:00
* Integer
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Integer.try_convert is added. [[Feature #15211]]
Add Integer.try_convert [Feature #15211]
2018-10-07 00:02:46 -04:00
Update documentation for Module#{private,public,protected,module_function} Also, update NEWS for this change and the Kernel#load change.
2021-11-18 13:51:14 -05:00
* Kernel
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Kernel#load now accepts a module as the second argument,
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
and will load the file using the given module as the
top-level module. [[Feature #6210]]
Update documentation for Module#{private,public,protected,module_function} Also, update NEWS for this change and the Kernel#load change.
2021-11-18 13:51:14 -05:00
NEWS.md document String#unpack offset and Marshal.load freeze arguments
2021-12-13 03:45:29 -05:00
* Marshal
* Marshal.load now accepts a `freeze: true` option.
All returned objects are frozen except for `Class` and
`Module` instances. Strings are deduplicated. [[Feature #18148]]
NEWS for [Feature #18172] [ci skip]
2021-09-16 06:55:31 -04:00
* MatchData
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* MatchData#match is added [[Feature #18172]]
NEWS for [Feature #18172] [ci skip]
2021-09-16 06:55:31 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* MatchData#match_length is added [[Feature #18172]]
NEWS for [Feature #18172] [ci skip]
2021-09-16 06:55:31 -04:00
Add {Method,UnboundMethod}#{public?,private?,protected?} These methods allow for checking whether the method has that visibility. Implements [Feature #11689]
2021-10-27 18:36:00 -04:00
* Method/UnboundMethod
[DOC] Get rid of headings in list items The current RDoc Markdown parser parses the list item starting with `#` as a heading line.
2021-12-13 00:13:46 -05:00
* Method#public?, Method#private?, Method#protected?,
UnboundMethod#public?, UnboundMethod#private?,
UnboundMethod#protected? have been added. [[Feature #11689]]
Add {Method,UnboundMethod}#{public?,private?,protected?} These methods allow for checking whether the method has that visibility. Implements [Feature #11689]
2021-10-27 18:36:00 -04:00
Make Module#prepend affect ancestor chain even if argument already included in receiver Previously, if a class included a module and then prepended the same module, the prepend had no effect. This changes the behavior so that the prepend has an effect unless the module is already prepended the receiver. While here, rename the origin_seen variable in include_modules_at, since it is misleading. The variable tracks whether c has been seen, not whether the origin of klass has been. Fixes [Bug #17423]
2021-01-14 14:59:25 -05:00
* Module
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Module#prepend now modifies the ancestor chain if the receiver
already includes the argument. Module#prepend still does not
modify the ancestor chain if the receiver has already prepended
the argument. [[Bug #17423]]
Make Module#prepend affect ancestor chain even if argument already included in receiver Previously, if a class included a module and then prepended the same module, the prepend had no effect. This changes the behavior so that the prepend has an effect unless the module is already prepended the receiver. While here, rename the origin_seen variable in include_modules_at, since it is misleading. The variable tracks whether c has been seen, not whether the origin of klass has been. Fixes [Bug #17423]
2021-01-14 14:59:25 -05:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Module#private, #public, #protected, and #module_function will
now return their arguments. If a single argument is given, it
is returned. If no arguments are given, nil is returned. If
multiple arguments are given, they are returned as an array.
[[Feature #12495]]
Update documentation for Module#{private,public,protected,module_function} Also, update NEWS for this change and the Kernel#load change.
2021-11-18 13:51:14 -05:00
NEWS.md: Mention Process._fork [[Feature #17795]]
2021-11-08 13:38:42 -05:00
* Process
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Process.\_fork is added. This is a core method for fork(2).
Do not call this method directly; it is called by existing
fork methods: Kernel.#fork, Process.fork, and IO.popen("-").
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
Application monitoring libraries can overwrite this method to
hook fork events. [[Feature #17795]]
NEWS.md: Mention Process._fork [[Feature #17795]]
2021-11-08 13:38:42 -05:00
Warn Struct#initialize with only keyword args (#4070) * Warn Struct#initialize with only keyword args A part of [Feature #16806] * Do not warn if `keyword_init: false` is explicitly specified * Add a NEWS entry * s/in/from/ * Make sure all fields are initialized
2021-01-17 04:35:54 -05:00
* Struct
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Passing only keyword arguments to Struct#initialize is warned.
You need to use a Hash literal to set a Hash to a first member.
[[Feature #16806]]
Warn Struct#initialize with only keyword args (#4070) * Warn Struct#initialize with only keyword args A part of [Feature #16806] * Do not warn if `keyword_init: false` is explicitly specified * Add a NEWS entry * s/in/from/ * Make sure all fields are initialized
2021-01-17 04:35:54 -05:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* StructClass#keyword_init? is added [[Feature #18008]]
Add tests and NEWS [Feature #18008]
2021-07-15 05:21:49 -04:00
Mention update to Unicode Version 13.0.0 and Emoji Version 13.1 Mention the update to Unicode Version 13.0.0 and Unicode Emoji Version 13.1 in NEWS.md. This completes issue #17750. [ci skip]
2021-08-17 04:07:01 -04:00
* String
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Update Unicode version to 13.0.0 [[Feature #17750]]
and Emoji version to 13.0 [[Feature #18029]]
Mention update to Unicode Version 13.0.0 and Emoji Version 13.1 Mention the update to Unicode Version 13.0.0 and Unicode Emoji Version 13.1 in NEWS.md. This completes issue #17750. [ci skip]
2021-08-17 04:07:01 -04:00
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
* String#unpack and String#unpack1 now accept an `offset:` keyword
NEWS.md document String#unpack offset and Marshal.load freeze arguments
2021-12-13 03:45:29 -05:00
argument to start the unpacking after an arbitrary number of bytes
have been skipped. If `offset` is outside of the string bounds
`ArgumentError` is raised. [[Feature #18254]]
The Queue constructor should take an initial set of objects Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
2021-02-11 05:14:18 -05:00
* Queue
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Queue#initialize now accepts an Enumerable of initial values.
[[Feature #17327]]
The Queue constructor should take an initial set of objects Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
2021-02-11 05:14:18 -05:00
Add NEWS about 46655156dcc37509dcb69fcd0717c110eb1c624a * Add Thread#native_thread_id [Feature #17853]
2021-05-26 02:18:16 -04:00
* Thread
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Thread#native_thread_id is added. [[Feature #17853]]
Add NEWS about 46655156dcc37509dcb69fcd0717c110eb1c624a * Add Thread#native_thread_id [Feature #17853]
2021-05-26 02:18:16 -04:00
[DOC] NEWS for Thread::Backtrace.limit [Feature #17479]
2021-02-15 02:06:43 -05:00
* Thread::Backtrace
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Thread::Backtrace.limit, which returns the value to limit backtrace
length set by `--backtrace-limit` command line option, is added.
[[Feature #17479]]
[DOC] NEWS for Thread::Backtrace.limit [Feature #17479]
2021-02-15 02:06:43 -05:00
NEWS.md: Mention `in:` option of Time.new [Feature #17485]
2021-12-13 00:19:31 -05:00
* Time
* Time.new now accepts optional `in:` keyword argument for the
timezone, as well as `Time.at` and `Time.now`, so that is now
you can omit minor arguments to `Time.new`. [[Feature #17485]]
NEWS.md: RFC 3339 UTC for unknown offset local time [Feature #17544]
2021-12-13 00:28:59 -05:00
* Time#strftime supports RFC 3339 UTC for unknown offset local
time, `-0000`, as `%-z`. [[Feature #17544]]
add a NEWS entry for `TracePoint.allow_reenter`
2021-12-13 00:02:07 -05:00
* TracePoint
Fix a typo [ci skip]
2021-12-21 03:44:48 -05:00
* TracePoint.allow_reentry is added to allow reenter while TracePoint
add a NEWS entry for `TracePoint.allow_reenter`
2021-12-13 00:02:07 -05:00
callback.
NEWS.md: One more surrounding brackets for the ticket
2021-12-13 07:20:12 -05:00
[[Feature #15912]]
add a NEWS entry for `TracePoint.allow_reenter`
2021-12-13 00:02:07 -05:00
Add NEWS entry for [Feature #16043]
2021-02-16 04:12:47 -05:00
* $LOAD_PATH
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* $LOAD_PATH.resolve_feature_path does not raise. [[Feature #16043]]
Add NEWS entry for [Feature #16043]
2021-02-16 04:12:47 -05:00
Add fiber scheduler news.
2021-06-22 07:14:45 -04:00
* Fiber Scheduler
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Add support for `Addrinfo.getaddrinfo` using `address_resolve` hook.
[[Feature #17370]]
Add fiber scheduler news.
2021-06-22 07:14:45 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Introduce non-blocking `Timeout.timeout` using `timeout_after` hook.
[[Feature #17470]]
Add fiber scheduler news.
2021-06-22 07:14:45 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Introduce new scheduler hooks `io_read` and `io_write` along with a
low level `IO::Buffer` for zero-copy read/write. [[Feature #18020]]
IO::Buffer for scheduler interface.
2021-07-02 06:41:16 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* IO hooks `io_wait`, `io_read`, `io_write`, receive the original IO object
where possible. [[Bug #18003]]
Add fiber scheduler news.
2021-06-22 07:14:45 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Make `Monitor` fiber-safe. [[Bug #17827]]
Add fiber scheduler news.
2021-06-22 07:14:45 -04:00
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* Replace copy coroutine with pthread implementation. [[Feature #18015]]
Replace copy coroutine with pthread implementation.
2021-06-25 18:17:26 -04:00
Deprecate include/prepend in refinements and add Refinement#import_methods instead Refinement#import_methods imports methods from modules. Unlike Module#include, it copies methods and adds them into the refinement, so the refinement is activated in the imported methods. [Bug #17429] [ruby-core:101639]
2021-10-21 03:21:08 -04:00
* Refinement
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-07 08:00:23 -05:00
* New class which represents a module created by Module#refine.
`include` and `prepend` are deprecated, and `import_methods` is added
instead. [[Bug #17429]]
Deprecate include/prepend in refinements and add Refinement#import_methods instead Refinement#import_methods imports methods from modules. Unlike Module#include, it copies methods and adds them into the refinement, so the refinement is activated in the imported methods. [Bug #17429] [ruby-core:101639]
2021-10-21 03:21:08 -04:00
[DOC] Separated parenthesized notes from subsection headings As the headings become link anchors, remove less useful notes. [ci skip]
2020-03-03 03:37:51 -05:00
## Stdlib updates
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* The following default gem are updated.
Update default gems list at f51811ca75894f5227fb2dd9f2f61f [ci skip]
2021-12-21 00:57:28 -05:00
* RubyGems 3.3.0
Update stdlib version at ded33ed5b8d923b0bb707b4e617ba0 [ci skip]
2021-12-15 04:00:47 -05:00
* base64 0.1.1
* benchmark 0.2.0
* bigdecimal 3.1.0.dev
Update default gems list at f51811ca75894f5227fb2dd9f2f61f [ci skip]
2021-12-21 00:57:28 -05:00
* bundler 2.3.0
Update stdlib version at ded33ed5b8d923b0bb707b4e617ba0 [ci skip]
2021-12-15 04:00:47 -05:00
* cgi 0.3.1
* csv 3.2.1
* date 3.2.2
* did_you_mean 1.6.0.pre.alpha
* digest 3.1.0.pre3
* drb 2.1.0
* erb 2.2.3
* error_highlight 0.2.0
* etc 1.3.0
* fcntl 1.0.1
* fiddle 1.1.0
* fileutils 1.6.0
* find 0.1.1
* io-console 0.5.9
* io-wait 0.2.1
* ipaddr 1.2.3
* irb 1.3.8.pre.11
* json 2.6.1
Update logger version on NEWS
2021-12-20 04:02:19 -05:00
* logger 1.5.0
Update stdlib version at ded33ed5b8d923b0bb707b4e617ba0 [ci skip]
2021-12-15 04:00:47 -05:00
* net-http 0.2.0
* net-protocol 0.1.2
* nkf 0.1.1
* open-uri 0.2.0
* openssl 3.0.0.pre
* optparse 0.2.0
* ostruct 0.5.2
* pathname 0.2.0
Update pp version on NEWS
2021-12-19 22:46:11 -05:00
* pp 0.3.0
Update stdlib version at ded33ed5b8d923b0bb707b4e617ba0 [ci skip]
2021-12-15 04:00:47 -05:00
* prettyprint 0.1.1
Update default gems list at 706c7a27fa00f72ec4f5d2f3af8151 [ci skip]
2021-12-20 04:26:42 -05:00
* psych 4.0.3
Update stdlib version at ded33ed5b8d923b0bb707b4e617ba0 [ci skip]
2021-12-15 04:00:47 -05:00
* racc 1.6.0
* rdoc 6.3.2
* readline-ext 0.1.3
Update stdlib version at 333865e56f594f365f2b3b4ef0f86f [ci skip]
2021-12-15 07:52:15 -05:00
* reline 0.2.8.pre.11
Update stdlib version at ded33ed5b8d923b0bb707b4e617ba0 [ci skip]
2021-12-15 04:00:47 -05:00
* resolv 0.2.1
* rinda 0.1.1
* ruby2_keywords 0.0.5
* securerandom 0.1.1
* set 1.0.2
* stringio 3.0.1
* strscan 3.0.1
* tempfile 0.1.2
* time 0.2.0
* timeout 0.2.0
* tmpdir 0.1.2
* un 0.2.0
* uri 0.11.0
* yaml 0.2.0
* zlib 2.1.1
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* The following bundled gems are updated.
Update stdlib version [ci skip]
2021-12-15 04:53:16 -05:00
* minitest 5.15.0
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* power_assert 2.0.1
* rake 13.0.6
Update bundled gems list at 2021-12-20
2021-12-20 02:05:44 -05:00
* test-unit 3.5.3
Update bundled gems list at 2021-12-17
2021-12-17 11:18:25 -05:00
* rexml 3.2.5
Update stdlib version [ci skip]
2021-12-14 02:06:50 -05:00
* rbs 1.8.1
Update bundled gems list at 2021-12-20
2021-12-20 04:50:16 -05:00
* typeprof 0.21.0
More indentation in NEWS.md [ci skip] The current Markdown implementation of RDoc requires list contents to be indented 4 columns except for the first paragraph. Maybe fixed as other implementations in the future.
2021-12-05 05:08:25 -05:00
* The following default gems are now bundled gems.
Update bundled gems list at 2021-12-17
2021-12-17 11:18:25 -05:00
* net-ftp 0.1.3
* net-imap 0.2.2
* net-pop 0.1.1
* net-smtp 0.3.1
* matrix 0.4.2
* prime 0.1.2
Update bundled gems list at 2021-12-17
2021-12-17 14:21:56 -05:00
* debug 1.4.0
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
NEWS.md: Fix a typo
2021-12-17 06:34:14 -05:00
* Coverage measurement now supports suspension. You can use `Coverage.suspend`
NEWS.md: Mention suspendatble coverage [Feature #18176]
2021-12-12 23:53:34 -05:00
to stop the measurement temporarily, and `Coverage.resume` to restart it.
See [[Feature #18176]] in detail.
NEWS.md: move of Random::Formatter [Feature #18190]
2021-12-13 05:13:21 -05:00
* Random::Formatter is moved to random/formatter.rb, so that you can
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
use `Random#hex`, `Random#base64`, and so on without SecureRandom.
NEWS.md: move of Random::Formatter [Feature #18190]
2021-12-13 05:13:21 -05:00
[[Feature #18190]]
[DOC] Separated parenthesized notes from subsection headings As the headings become link anchors, remove less useful notes. [ci skip]
2020-03-03 03:37:51 -05:00
## Compatibility issues
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
Note: Excluding feature bug fixes.
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
Add fiber scheduler news.
2021-06-22 07:14:45 -04:00
* `rb_io_wait_readable`, `rb_io_wait_writable` and `rb_wait_for_single_fd` are
deprecated in favour of `rb_io_maybe_wait_readable`,
`rb_io_maybe_wait_writable` and `rb_io_maybe_wait` respectively.
`rb_thread_wait_fd` and `rb_thread_fd_writable` are deprecated. [[Bug #18003]]
NEWS.md: add an example, add references, and move some items
2020-08-24 02:38:03 -04:00
## Stdlib compatibility issues
Added sdbm entry to NEWS
2020-06-18 08:11:19 -04:00
Update NEWS.md about deprecation
2021-01-21 01:02:24 -05:00
* `ERB#initialize` warns `safe_level` and later arguments even without -w.
[[Feature #14256]]
add NEWS entries about debug.gem
2021-10-19 21:18:54 -04:00
* `lib/debug.rb` is replaced with `debug.gem`
NEWS.md: Describe the change of the default width of `pp` [Feature #12913]
2021-12-06 22:07:28 -05:00
* `Kernel#pp` in `lib/pp.rb` uses the width of `IO#winsize` by default.
This means that the output width is automatically changed depending on
your terminal size. [[Feature #12913]]
NEWS.md: reduce headings level [ci skip] As the only h2 did not have its exclusively owned body text, merged it to the first paragraph. Then pulled up h3 and deeper headings.
2020-01-18 03:46:52 -05:00
## C API updates
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
add NEWS entry for https://github.com/ruby/ruby/pull/4815
2021-09-22 04:59:28 -04:00
* Documented. [[GH-4815]]
[ci skip] Update NEWS.md for [Feature #18290]
2021-11-08 16:33:04 -05:00
* `rb_gc_force_recycle` is deprecated and has been changed to a no-op.
[[Feature #18290]]
NEWS.md: reduce headings level [ci skip] As the only h2 did not have its exclusively owned body text, merged it to the first paragraph. Then pulled up h3 and deeper headings.
2020-01-18 03:46:52 -05:00
## Implementation improvements
NEWS.md: converted from NEWS and NEWS is deleted
2020-01-14 22:42:47 -05:00
add NEWS about the improvement of `Struct`
2021-12-06 03:19:42 -05:00
* `instance_eval` and `instance_exec` now only allocate a singleton class when
required, avoiding extra objects and improving performance. [[GH-5146]]
* The performance of `Struct` accessors is improved. [[GH-5131]]
add a NEWS entry for `mandatory_only?`
2021-12-06 12:03:06 -05:00
* `mandatory_only?` builtin special form to improve performance on
builtin methods. [[GH-5112]]
[ci skip] NEWS.md: Add Variable Width Allocation
2021-12-13 09:46:34 -05:00
* Experimental feature Variable Width Allocation in the garbage collector.
[ci skip] NEWS.md: Update Variable Width Allocation
2021-12-13 10:18:39 -05:00
This feature is turned off by default and can be enabled by compiling Ruby
with flag `USE_RVARGC=1` set. [[Feature #18045]] [[Feature #18239]]
[ci skip] NEWS.md: Add Variable Width Allocation
2021-12-13 09:46:34 -05:00
Rename --jit to --mjit (#5248) * Rename --jit to --mjit [Feature #18349] * Fix a few more --jit references * Fix MJIT Actions * More s/jit/mjit/ and re-introduce --disable-jit * Update NEWS.md * Fix test_bug_reporter_add
2021-12-13 19:08:01 -05:00
## JIT
Add NEWS entries about JIT optimizations and a related VM improvement. JIT related commits: * Code size reduction * Deduplicate functions on JIT compaction 818d6d33368a396d9cd3d1a34a84015a9e76c5c8 * Avoid always inlining cold paths of ivar fcd257629063a345c48ff2d8057fa8ab910881f2 * Inline only fast path of rb_class_of b16a2aa938d091c387a7437d94dac7f7bb829ba2 * Eliminate a call instruction on deopt 61b14bb32b7e62760225cb2207df5fe87e5339ab * Cold path partitioning * Mark method call slow paths as COLDFUNC 0e5a58b6bf6aae72b6290a8d68e0a1b6d9eb4f79 * Mark vm_stackoverflow as NOINLINE COLDFUNC 9d71373c237876038cbac63bb0132907a78288a2 * Create mjit_exec_slowpath and mark it as NOINLINE COLDFUNC 083a17a82ad4c1f80cfb9e84cfb1bff5586470b1 * Primitive.attr! 'inline' / Integer#zero? 7561db8c009bb79a75024fa4ed0350bfb3d0626c * Kernel#class 946e5cc668f66a4a0b79461047d3fcba8b71eef0 * (more to come...) * Properly generate opt_send for cfunc cc 7982dc1dfd5df000b7361ccb7bc820da4f3547b8 * Optimize exivar access b736ea63bd4ce4e2fc81dfa73938b39fa70f659c * Make JIT-ed leave leaf 151f8be40d385ada2ebf7feb84210ed7db7ef4df * Inline vm_call_cfunc b9d3ceee8f8e4fade1eddc0c18abee59f9c1eee7 VM: * Enable fastpath on invokesuper 5c2768181382bf84137759efea66f3aaf212665d * History: https://speakerdeck.com/k0kubun/ruby-3-samituto?slide=40 (in Japanese)
2020-06-26 03:54:05 -04:00
Rename --jit to --mjit (#5248) * Rename --jit to --mjit [Feature #18349] * Fix a few more --jit references * Fix MJIT Actions * More s/jit/mjit/ and re-introduce --disable-jit * Update NEWS.md * Fix test_bug_reporter_add
2021-12-13 19:08:01 -05:00
* Rename Ruby 3.0's `--jit` to `--mjit`, and alias `--jit` to `--yjit`
on non-Windows x86-64 platforms and to `--mjit` on others.
### MJIT
* The default `--mjit-max-cache` is changed from 100 to 10000.
Change the default --jit-max-cache to 10000 This is useful for large applications like Rails. https://k0kubun.medium.com/ruby-3-jit-can-make-rails-faster-756310f235a
2021-06-01 01:00:14 -04:00
Don't cancel JIT-ed code on TracePoint :class events get enabled
2021-08-13 02:19:15 -04:00
* JIT-ed code is no longer cancelled when a TracePoint for class events
is enabled.
Note about 07c05b6fe931337e928a89ac5ebf654862dc0eca
2021-06-03 01:25:48 -04:00
* The JIT compiler no longer skips compilation of methods longer than
1000 instructions.
Rename --jit to --mjit (#5248) * Rename --jit to --mjit [Feature #18349] * Fix a few more --jit references * Fix MJIT Actions * More s/jit/mjit/ and re-introduce --disable-jit * Update NEWS.md * Fix test_bug_reporter_add
2021-12-13 19:08:01 -05:00
* `--mjit-verbose` and `--mjit-warning` output "JIT cancel" when JIT-ed
Print JIT cancel when all JIT-ed code is cancelled
2021-08-13 01:54:40 -04:00
code is disabled because TracePoint or GC.compact is used.
Add bit about YJIT to NEWS.md
2021-10-20 15:51:07 -04:00
### YJIT: New experimental in-process JIT compiler
Add link to YJIT blog post to NEWS.md Requested by @nurse
2021-10-21 12:49:58 -04:00
New JIT compiler available as an experimental feature. [[Feature #18229]]
See [this blog post](https://shopify.engineering/yjit-just-in-time-compiler-cruby
) introducing the project.
Add bit about YJIT to NEWS.md
2021-10-20 15:51:07 -04:00
* Disabled by default, use `--yjit` command-line option to enable YJIT.
* Performance improvements on most real-world software, up to 22% on railsbench, 39% on liquid-render.
* Fast warm-up times.
* Limited to macOS & Linux on x86-64 platforms for now.
Fix some typos in NEWS.md.
2020-11-10 12:15:57 -05:00
## Static analysis
NEWS.md: mention TypeProf
2020-10-20 00:16:19 -04:00
### RBS
Update NEWS about RBS (#3579)
2020-09-25 04:08:39 -04:00
NEWS.md: Add link to `rbs collection` documentation
2021-12-16 23:54:23 -05:00
* [rbs collection](https://github.com/ruby/rbs/blob/master/docs/collection.md) has been introduced to manage gems’ RBSs.
NEWS.md: Describe changes of RBS
2021-12-16 23:46:09 -05:00
* Many signatures for built-in and standard libraries have been added/updated.
* It includes many bug fixes and performance improvements too.
See the [CHANGELOG.md](https://github.com/ruby/rbs/blob/master/CHANGELOG.md) for more information.
NEWS.md: mention TypeProf
2020-10-20 00:16:19 -04:00
### TypeProf
NEWS.md: Add error_highlight section
2021-10-19 22:05:05 -04:00
* [Experimental IDE support](https://github.com/ruby/typeprof/blob/master/doc/ide.md) has been implemented.
* Many bug fixes and performance improvements since Ruby 3.0.0.
add NEWS entries about debug.gem
2021-10-19 21:18:54 -04:00
## Debugger
* A new debugger [debug.gem](https://github.com/ruby/debug) is bundled.
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
debug.gem is a fast debugger implementation, and it provides many features
like remote debugging, colorful REPL, IDE (VSCode) integration, and more.
add NEWS entries about debug.gem
2021-10-19 21:18:54 -04:00
It replaces `lib/debug.rb` standard library.
* `rdbg` command is also installed into `bin/` directory to start and control
debugging execution.
NEWS.md: Add error_highlight section
2021-10-19 22:05:05 -04:00
## error_highlight
NEWS.md: Use more descriptive example for error_highlight
2021-12-12 23:49:39 -05:00
A built-in gem called error_highlight has been introduced.
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
It shows fine-grained error locations in the backtrace.
NEWS.md: Use more descriptive example for error_highlight
2021-12-12 23:49:39 -05:00
Example: `title = json[:article][:title]`
If `json` is nil, it shows:
```
$ ruby test.rb
test.rb:2:in `<main>': undefined method `[]' for nil:NilClass (NoMethodError)
title = json[:article][:title]
^^^^^^^^^^
```
If `json[:article]` returns nil, it shows:
NEWS.md: Add error_highlight section
2021-10-19 22:05:05 -04:00
```
$ ruby test.rb
NEWS.md: Use more descriptive example for error_highlight
2021-12-12 23:49:39 -05:00
test.rb:2:in `<main>': undefined method `[]' for nil:NilClass (NoMethodError)
NEWS.md: Add error_highlight section
2021-10-19 22:05:05 -04:00
NEWS.md: Use more descriptive example for error_highlight
2021-12-12 23:49:39 -05:00
title = json[:article][:title]
^^^^^^^^
NEWS.md: Add error_highlight section
2021-10-19 22:05:05 -04:00
```
NEWS.md: Use more descriptive example for error_highlight
2021-12-12 23:49:39 -05:00
This feature is enabled by default.
NEWS.md: Add error_highlight section
2021-10-19 22:05:05 -04:00
You can disable it by using a command-line option `--disable-error_highlight`.
See [the repository](https://github.com/ruby/error_highlight) in detail.
NEWS.md: reduce headings level [ci skip] As the only h2 did not have its exclusively owned body text, merged it to the first paragraph. Then pulled up h3 and deeper headings.
2020-01-18 03:46:52 -05:00
## Miscellaneous changes
NEWS: [Feature #17312] [ci skip]
2021-01-02 02:42:45 -05:00
NEWS.md: mention lib/objspace/trace.rb [Feature #17762]
2021-05-16 19:49:53 -04:00
* lib/objspace/trace.rb is added, which is a tool for tracing the object
allocation. Just by requiring this file, tracing is started *immediately*.
Just by `Kernel#p`, you can investigate where an object was created.
Note that just requiring this file brings a large performance overhead.
Improve wording on NEWS.md
2021-12-15 11:24:31 -05:00
This is only for debugging purposes. Do not use this in production.
[NEWS] adjusted formats [ci skip]
2021-07-22 23:41:01 -04:00
[[Feature #17762]]
NEWS: [Feature #17312] [ci skip]
2021-01-02 02:42:45 -05:00
[NEWS] added [Feature #17798] [ci skip]
2021-07-22 23:41:34 -04:00
* Now exceptions raised in finalizers will be printed to `STDERR`, unless
`$VERBOSE` is `nil`. [[Feature #17798]]
NEWS.md: `ruby -run -e httpd` displays URLs to access [Feature #17847]
2021-12-13 00:57:28 -05:00
* `ruby -run -e httpd` displays URLs to access. [[Feature #17847]]
NEWS.md: Mention colorize command of un.rb https://github.com/ruby/un/pull/1
2021-12-13 19:28:09 -05:00
* Add `ruby -run -e colorize` to colorize Ruby code using
`IRB::Color.colorize_code`.
[NEWS] adjusted formats [ci skip]
2021-07-22 23:41:01 -04:00
[Bug #4443]: https://bugs.ruby-lang.org/issues/4443
Update documentation for Module#{private,public,protected,module_function} Also, update NEWS for this change and the Kernel#load change.
2021-11-18 13:51:14 -05:00
[Feature #6210]: https://bugs.ruby-lang.org/issues/6210
Anonymous block forwarding allows a method to forward a passed block to another method without having to provide a name for the block parameter. Implements [Feature #11256] Co-authored-by: Yusuke Endoh mame@ruby-lang.org Co-authored-by: Nobuyoshi Nakada nobu@ruby-lang.org
2021-11-18 15:44:19 -05:00
[Feature #11256]: https://bugs.ruby-lang.org/issues/11256
Add {Method,UnboundMethod}#{public?,private?,protected?} These methods allow for checking whether the method has that visibility. Implements [Feature #11689]
2021-10-27 18:36:00 -04:00
[Feature #11689]: https://bugs.ruby-lang.org/issues/11689
Fix a link [ci skip]
2021-03-16 01:07:27 -04:00
[Feature #12194]: https://bugs.ruby-lang.org/issues/12194
Update documentation for Module#{private,public,protected,module_function} Also, update NEWS for this change and the Kernel#load change.
2021-11-18 13:51:14 -05:00
[Feature #12495]: https://bugs.ruby-lang.org/issues/12495
Fix a link [ci skip]
2021-12-07 01:02:08 -05:00
[Feature #12913]: https://bugs.ruby-lang.org/issues/12913
Update NEWS.md about deprecation
2021-01-21 01:02:24 -05:00
[Feature #14256]: https://bugs.ruby-lang.org/issues/14256
[DOC] NEWS for [Feature #14579] [ci skip]
2021-09-11 06:13:53 -04:00
[Feature #14579]: https://bugs.ruby-lang.org/issues/14579
NEWS for [Feature #15198] [ci skip]
2021-04-16 03:12:10 -04:00
[Feature #15198]: https://bugs.ruby-lang.org/issues/15198
Add Integer.try_convert [Feature #15211]
2018-10-07 00:02:46 -04:00
[Feature #15211]: https://bugs.ruby-lang.org/issues/15211
add a NEWS entry for `TracePoint.allow_reenter`
2021-12-13 00:02:07 -05:00
[Feature #15912]: https://bugs.ruby-lang.org/issues/15912
Add NEWS entry for [Feature #16043]
2021-02-16 04:12:47 -05:00
[Feature #16043]: https://bugs.ruby-lang.org/issues/16043
Add news about allowing omission of parentheses in one-line pattern matching
2021-12-19 07:37:08 -05:00
[Feature #16182]: https://bugs.ruby-lang.org/issues/16182
Sort URLs by issue numbers [ci skip]
2021-12-19 09:43:39 -05:00
[Feature #16806]: https://bugs.ruby-lang.org/issues/16806
NEWS: [Feature #17312] [ci skip]
2021-01-02 02:42:45 -05:00
[Feature #17312]: https://bugs.ruby-lang.org/issues/17312
The Queue constructor should take an initial set of objects Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
2021-02-11 05:14:18 -05:00
[Feature #17327]: https://bugs.ruby-lang.org/issues/17327
Sort URLs by issue numbers [ci skip]
2021-10-27 03:55:15 -04:00
[Feature #17370]: https://bugs.ruby-lang.org/issues/17370
NEWS.md: `def foo = puts "Hello"` is now allowed [Feature #17398]
2021-12-13 00:01:40 -05:00
[Feature #17398]: https://bugs.ruby-lang.org/issues/17398
Pattern matching pin operator against expression [Feature #17411] This commit is based on the patch by @nobu.
2021-03-21 02:12:54 -04:00
[Feature #17411]: https://bugs.ruby-lang.org/issues/17411
[NEWS] adjusted formats [ci skip]
2021-07-22 23:41:01 -04:00
[Bug #17423]: https://bugs.ruby-lang.org/issues/17423
Sort URLs by issue numbers [ci skip]
2021-10-27 03:55:15 -04:00
[Bug #17429]: https://bugs.ruby-lang.org/issues/17429
[Feature #17470]: https://bugs.ruby-lang.org/issues/17470
[DOC] NEWS for Thread::Backtrace.limit [Feature #17479]
2021-02-15 02:06:43 -05:00
[Feature #17479]: https://bugs.ruby-lang.org/issues/17479
NEWS.md: Mention `in:` option of Time.new [Feature #17485]
2021-12-13 00:19:31 -05:00
[Feature #17485]: https://bugs.ruby-lang.org/issues/17485
NEWS.md: RFC 3339 UTC for unknown offset local time [Feature #17544]
2021-12-13 00:28:59 -05:00
[Feature #17544]: https://bugs.ruby-lang.org/issues/17544
update NEWS about last commits.
2021-10-22 12:38:05 -04:00
[Feature #17592]: https://bugs.ruby-lang.org/issues/17592
NEWS.md: `--disable-gems` is now just for debugging. [Feature #17684]
2021-12-13 00:19:21 -05:00
[Feature #17684]: https://bugs.ruby-lang.org/issues/17684
Add pattern matching pin support for instance/class/global variables Pin matching for local variables and constants is already supported, and it is fairly simple to add support for these variable types. Note that pin matching for method calls is still not supported without wrapping in parentheses (pin expressions). I think that's for the best as method calls are far more complex (arguments/blocks). Implements [Feature #17724]
2021-05-13 18:31:46 -04:00
[Feature #17724]: https://bugs.ruby-lang.org/issues/17724
Enumerable#tally with the resulting hash [Feature #17744]
2021-03-26 03:29:21 -04:00
[Feature #17744]: https://bugs.ruby-lang.org/issues/17744
Sort URLs by issue numbers [ci skip]
2021-10-27 03:55:15 -04:00
[Feature #17750]: https://bugs.ruby-lang.org/issues/17750
NEWS.md: mention lib/objspace/trace.rb [Feature #17762]
2021-05-16 19:49:53 -04:00
[Feature #17762]: https://bugs.ruby-lang.org/issues/17762
Fix a link [ci skip]
2021-11-08 21:30:03 -05:00
[Feature #17795]: https://bugs.ruby-lang.org/issues/17795
[NEWS] added [Feature #17798] [ci skip]
2021-07-22 23:41:34 -04:00
[Feature #17798]: https://bugs.ruby-lang.org/issues/17798
[NEWS] adjusted formats [ci skip]
2021-07-22 23:41:01 -04:00
[Bug #17827]: https://bugs.ruby-lang.org/issues/17827
NEWS.md: `ruby -run -e httpd` displays URLs to access [Feature #17847]
2021-12-13 00:57:28 -05:00
[Feature #17847]: https://bugs.ruby-lang.org/issues/17847
Sort URLs by issue numbers [ci skip]
2021-10-27 03:55:15 -04:00
[Feature #17853]: https://bugs.ruby-lang.org/issues/17853
[Bug #18003]: https://bugs.ruby-lang.org/issues/18003
Fix a link [ci skip]
2021-08-05 04:25:17 -04:00
[Feature #18008]: https://bugs.ruby-lang.org/issues/18008
Replace copy coroutine with pthread implementation.
2021-06-25 18:17:26 -04:00
[Feature #18015]: https://bugs.ruby-lang.org/issues/18015
IO::Buffer for scheduler interface.
2021-07-02 06:41:16 -04:00
[Feature #18020]: https://bugs.ruby-lang.org/issues/18020
Fix links [ci skip]
2021-08-22 09:27:29 -04:00
[Feature #18029]: https://bugs.ruby-lang.org/issues/18029
NEWS.md: sort [ci skip]
2021-12-13 10:03:37 -05:00
[Feature #18045]: https://bugs.ruby-lang.org/issues/18045
NEWS.md document String#unpack offset and Marshal.load freeze arguments
2021-12-13 03:45:29 -05:00
[Feature #18148]: https://bugs.ruby-lang.org/issues/18148
NEWS for [Feature #18172] [ci skip]
2021-09-16 06:55:31 -04:00
[Feature #18172]: https://bugs.ruby-lang.org/issues/18172
NEWS.md: Mention suspendatble coverage [Feature #18176]
2021-12-12 23:53:34 -05:00
[Feature #18176]: https://bugs.ruby-lang.org/issues/18176
NEWS.md: move of Random::Formatter [Feature #18190]
2021-12-13 05:13:21 -05:00
[Feature #18190]: https://bugs.ruby-lang.org/issues/18190
Fix links [ci skip]
2021-10-24 19:38:44 -04:00
[Feature #18229]: https://bugs.ruby-lang.org/issues/18229
NEWS.md: sort [ci skip]
2021-12-13 10:03:37 -05:00
[Feature #18239]: https://bugs.ruby-lang.org/issues/18239
NEWS.md document String#unpack offset and Marshal.load freeze arguments
2021-12-13 03:45:29 -05:00
[Feature #18254]: https://bugs.ruby-lang.org/issues/18254
Add Class#subclasses Implements [Feature #18273] Returns an array containing the receiver's direct subclasses without singleton classes.
2021-10-28 08:07:11 -04:00
[Feature #18273]: https://bugs.ruby-lang.org/issues/18273
Sort URLs by issue numbers [ci skip]
2021-12-05 06:31:58 -05:00
[Feature #18290]: https://bugs.ruby-lang.org/issues/18290
NEWS.md document String#unpack offset and Marshal.load freeze arguments
2021-12-13 03:45:29 -05:00
Add changes Enumerable#each_cons and each_slice in NEWS [ci skip]
2021-10-28 05:21:27 -04:00
[GH-1509]: https://github.com/ruby/ruby/pull/1509
add NEWS entry for https://github.com/ruby/ruby/pull/4815
2021-09-22 04:59:28 -04:00
[GH-4815]: https://github.com/ruby/ruby/pull/4815
add a NEWS entry for `mandatory_only?`
2021-12-06 12:03:06 -05:00
[GH-5112]: https://github.com/ruby/ruby/pull/5112
add NEWS about the improvement of `Struct`
2021-12-06 03:19:42 -05:00
[GH-5131]: https://github.com/ruby/ruby/pull/5131
NEWS for [GH-#5146] [ci skip] (#5210)
2021-12-03 15:58:09 -05:00
[GH-5146]: https://github.com/ruby/ruby/pull/5146
Copy permalink