summaryrefslogtreecommitdiff
path: root/NEWS.md
AgeCommit message (Collapse)Author
2021-10-27Sort URLs by issue numbers [ci skip]Kazuhiro NISHIYAMA
2021-10-27Update stdlib versionsKazuhiro NISHIYAMA
2021-10-26Add Class#descendantsJeremy Evans
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> Notes: Merged: https://github.com/ruby/ruby/pull/4974 Merged-By: jeremyevans <code@jeremyevans.net>
2021-10-25Fix links [ci skip]Kazuhiro NISHIYAMA
2021-10-24NEWS: StringScanner 3.0.1 is releasedSutou Kouhei
Notes: Merged: https://github.com/ruby/ruby/pull/5011
2021-10-24NEWS: CSV 3.2.1 is releasedSutou Kouhei
Notes: Merged: https://github.com/ruby/ruby/pull/5010
2021-10-23NEWS: Fiddle 1.1.0 is releasedSutou Kouhei
2021-10-23update NEWS about last commits.Koichi Sasada
2021-10-21Add link to YJIT blog post to NEWS.mdMaxime Chevalier-Boisvert
Requested by @nurse
2021-10-21Added version of readline-extHiroshi SHIBATA
2021-10-21Update the merged versions of default gems.Hiroshi SHIBATA
2021-10-21Deprecate include/prepend in refinements and add Refinement#import_methods ↵Shugo Maeda
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-20Add bit about YJIT to NEWS.mdMaxime Chevalier-Boisvert
Notes: Merged: https://github.com/ruby/ruby/pull/4997
2021-10-20Added entries about default gems and bundled gemsHiroshi SHIBATA
2021-10-20NEWS.md: Add error_highlight sectionYusuke Endoh
2021-10-20add NEWS entries about debug.gemKoichi Sasada
2021-09-22add NEWS entry for https://github.com/ruby/ruby/pull/4815卜部昌平
2021-09-16NEWS for [Feature #18172] [ci skip]Nobuyoshi Nakada
2021-09-16Add a newline [ci skip]Shugo Maeda
2021-09-16Add details of Hash value ommission [ci skip]Shugo Maeda
2021-09-11Add documentation and tests for keyword argument value omissionShugo Maeda
[Feature #14579]
2021-09-11[DOC] NEWS for [Feature #14579] [ci skip]Nobuyoshi Nakada
2021-09-11[DOC] Fixed indents in NEWS.md [ci skip]Nobuyoshi Nakada
2021-08-22Fix links [ci skip]Kazuhiro NISHIYAMA
2021-08-17Mention update to Unicode Version 13.0.0 and Emoji Version 13.1Martin Dürst
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-13Revert "Pause an MJIT worker when JIT is cancelled"Takashi Kokubun
This reverts commit b64f81c81729bbc248d19af01cafde88eb60fdc7. It seems to cause a problem in --jit / --jit-wait CIs. Reverting for now.
2021-08-12Don't cancel JIT-ed code on TracePoint :classTakashi Kokubun
events get enabled
2021-08-12Pause an MJIT worker when JIT is cancelledTakashi Kokubun
2021-08-12Print JIT cancel when all JIT-ed code is cancelledTakashi Kokubun
2021-08-05Fix a link [ci skip]Kazuhiro NISHIYAMA
2021-07-23[NEWS] added [Feature #17798] [ci skip]Nobuyoshi Nakada
2021-07-23[NEWS] adjusted formats [ci skip]Nobuyoshi Nakada
2021-07-17One-line pattern matching is no longer experimentalKazuki Tsujimoto
https://github.com/ruby/dev-meeting-log/blob/master/DevelopersMeeting20210715Japan.md#feature-17724-make-the-pin-operator-support-instanceclassglobal-variables-jeremyevans0
2021-07-16Add Integer.try_convert [Feature #15211]Nobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/4654
2021-07-16Added code fence to the example in [Feature #17724] [ci skip]Nobuyoshi Nakada
2021-07-15Add pattern matching pin support for instance/class/global variablesJeremy Evans
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] Notes: Merged: https://github.com/ruby/ruby/pull/4502
2021-07-15Add tests and NEWS [Feature #18008]NARUSE, Yui
2021-07-15Fix typo in flag in NEWS.mdPatrik Ragnarsson
Notes: Merged: https://github.com/ruby/ruby/pull/4653
2021-07-01Replace copy coroutine with pthread implementation.Samuel Williams
2021-06-23Fix a link [ci skip]Kazuhiro NISHIYAMA
2021-06-22Fix NEWS formatting.Samuel Williams
2021-06-22Add fiber scheduler news.Samuel Williams
Notes: Merged: https://github.com/ruby/ruby/pull/4593
2021-06-02Note about 07c05b6fe931337e928a89ac5ebf654862dc0ecaTakashi Kokubun
2021-05-31Change the default --jit-max-cache to 10000Takashi Kokubun
This is useful for large applications like Rails. https://k0kubun.medium.com/ruby-3-jit-can-make-rails-faster-756310f235a
2021-05-26Add NEWS about 46655156dcc37509dcb69fcd0717c110eb1c624aNARUSE, Yui
* Add Thread#native_thread_id [Feature #17853]
2021-05-17NEWS.md: mention lib/objspace/trace.rb [Feature #17762]Yusuke Endoh
2021-04-21Evaluate multiple assignment left hand side before right hand sideJeremy Evans
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] Notes: Merged: https://github.com/ruby/ruby/pull/4390 Merged-By: jeremyevans <code@jeremyevans.net>
2021-04-16NEWS for [Feature #15198] [ci skip]Nobuyoshi Nakada
2021-03-26Enumerable#tally with the resulting hash [Feature #17744]Nobuyoshi Nakada
Notes: Merged: https://github.com/ruby/ruby/pull/4318 Merged-By: nobu <nobu@ruby-lang.org>
2021-03-21Pattern matching pin operator against expression [Feature #17411]Kazuki Tsujimoto
This commit is based on the patch by @nobu.
generated by cgit v1.2.3 (git 2.25.1) at 2024-05-08 04:57:32 +0000