aboutsummaryrefslogtreecommitdiffstats
path: root/NEWS.md
Commit message (Collapse)AuthorAgeFilesLines
* freeze all Range objects.v3_0_0_preview1Koichi Sasada2020-09-251-0/+4
| | | | | Matz want to try to freeze all Range objects. [Feature #15504]
* NEWS.md: Add memory view entryKenta Murata2020-09-251-0/+11
| | | | | | | | | The memory view interface added at 890bc2cdde is experimental new C-API set. This feature permits extension libraries to share a memory area that contains such a numerical array and a bitmap image. This is designed by referring to Python's buffer protocol. [[Feature #13767]] [[Feature #14722]]
* Update NEWS about RBS (#3579)Soutaro Matsumoto2020-09-251-0/+13
|
* Describe resolv_timeout in NEWSMasaki Matsushita2020-09-251-0/+9
|
* Update the version number of rubygems and bundler at NEWS.mdHiroshi SHIBATA2020-09-231-2/+2
|
* Add NEWS about `Fiber#backtrace` and `Fiber#backtrace_locations`.Samuel Williams2020-09-211-0/+3
|
* Update NEWS & documentation relating to scheduler.Samuel Williams2020-09-211-3/+44
|
* Sort links in NEWS.md by URI [ci skip]Kazuhiro NISHIYAMA2020-09-171-1/+1
|
* Add NEWS entry for [Feature #16792]Benoit Daloze2020-09-171-0/+7
|
* Interpolated strings are no longer frozen with frozen-string-literal: trueBenoit Daloze2020-09-151-0/+4
| | | | | * Remove freezestring instruction since this was the only usage for it. * [Feature #17104]
* Add IRB and Reline update for NEWS of 3.0.0-preview1aycabta2020-09-151-0/+8
|
* add NEW entries about Ractor and new method cache.Koichi Sasada2020-09-141-1/+12
|
* Added promoted libraries to default gems section on NEWSHiroshi SHIBATA2020-09-141-0/+10
|
* Revert the related commits about `Tempfile.open` change.Hiroshi SHIBATA2020-09-091-10/+0
| | | | | Start with https://github.com/ruby/ruby/commit/fa21985a7a2f8f52a8bd82bd12a724e9dca74934 to https://github.com/ruby/ruby/commit/d7492a0be885ea9f2b9f71e3e95582f9a859c439
* Sort links in NEWS.md by URI [ci skip]Nobuyoshi Nakada2020-09-041-12/+12
|
* Added Symbol#nameNobuyoshi Nakada2020-09-041-0/+7
| | | https://bugs.ruby-lang.org/issues/16150#change-87446
* Support passing a category to `Warning.warn`eileencodes2020-09-011-0/+8
| | | | | | | | | | | | | | | | | | | | | | This change adds a `category` kwarg to make it easier to monkey patch `Warning.warn`. Warnings already have a category, but that warning isn't exposed. This implements a way to get the category so that warnings with a specific category, like deprecated, can be treated differently than other warnings in an application. The change here does an arity check on the method to support backwards compatibility for applications that may already have a warning monkey patch. For our usecase we want to `raise` for deprecation warnings in order to get the behavior for the next Ruby version. For example, now that we fixed all our warnings and deployed Ruby 2.7 to production, we want to be able to have deprecation warnings behave like they would in 3.0: raise an error. For other warnings, like uninialized constants, that behavior won't be removed from Ruby in the next version, so we don't need to raise errors. Co-authored-by: Aaron Patterson <tenderlove@ruby-lang.org>
* Update version to 3.0.0 in NEWS.mdKazuhiro NISHIYAMA2020-08-311-1/+1
|
* [DOC] Fixed wording [ci skip]Nobuyoshi Nakada2020-08-311-1/+1
|
* [DOC] Indent a code block in NEWS [ci skip]Nobuyoshi Nakada2020-08-311-9/+8
|
* Sync with ruby/tempfile@aa9ea12d94a905161cbd79af1ad9ab427f250f4eBenoit Daloze2020-08-291-0/+10
|
* Some fixes in NEWS.mdBenoit Daloze2020-08-291-3/+3
|
* Added entry for changes of default gemsHiroshi SHIBATA2020-08-241-0/+20
|
* Fix links [ci skip]Kazuhiro NISHIYAMA2020-08-241-1/+4
|
* NEWS.md: add an example, add references, and move some itemsYusuke Endoh2020-08-241-13/+21
|
* Avoid duplicated "when"s [ci skip]Takashi Kokubun2020-06-261-2/+2
|
* Add a NEWS placeholder for disposable cc [ci skip]Takashi Kokubun2020-06-261-0/+5
| | | | asked by ko1 to put this.
* Add NEWS entries about JIT optimizationsTakashi Kokubun2020-06-261-0/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Make Integer#zero? a separated method and builtin (#3226)Takashi Kokubun2020-06-201-0/+2
| | | | | | | A prerequisite to fix https://bugs.ruby-lang.org/issues/15589 with JIT. This commit alone doesn't make a significant difference yet, but I thought this commit should be committed independently. This method override was discussed in [Misc #16961].
* Added sdbm entry to NEWSHiroshi SHIBATA2020-06-191-0/+4
|
* Add links [ci skip]Kazuhiro NISHIYAMA2020-06-191-0/+5
|
* Update NEWS.md [ci skip]Jeremy Evans2020-06-181-5/+29
|
* NEWS about Hash#except ENV#except [Feature #15822]Nobuyoshi Nakada2020-06-181-0/+13
|
* Introduce find pattern [Feature #16828]Kazuki Tsujimoto2020-06-141-0/+12
|
* Revert "Combine sweeping and moving"Aaron Patterson2020-06-091-8/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This reverts commit 02b216e5a70235f42f537e895d6f1afd05d8916a. This reverts commit 9b8825b6f94696c9659f93f5da9bf02644625f67. I found that combining sweep and move is not safe. I don't think that we can do compaction concurrently with _anything_ unless there is a read barrier installed. Here is a simple example. A class object is freed, and during it's free step, it tries to remove itself from its parent's subclass list. However, during the sweep step, the parent class was moved and the "currently being freed" class didn't have references updated yet. So we get a segv like this: ``` (lldb) bt * thread #1, name = 'ruby', stop reason = signal SIGSEGV * frame #0: 0x0000560763e344cb ruby`rb_st_lookup at st.c:320:43 frame #1: 0x0000560763e344cb ruby`rb_st_lookup(tab=0x2f7469672f6e6f72, key=3809, value=0x0000560765bf2270) at st.c:1010 frame #2: 0x0000560763e8f16a ruby`rb_search_class_path at variable.c:99:9 frame #3: 0x0000560763e8f141 ruby`rb_search_class_path at variable.c:145 frame #4: 0x0000560763e8f141 ruby`rb_search_class_path(klass=94589785585880) at variable.c:191 frame #5: 0x0000560763ec744e ruby`rb_vm_bugreport at vm_dump.c:996:17 frame #6: 0x0000560763f5b958 ruby`rb_bug_for_fatal_signal at error.c:675:5 frame #7: 0x0000560763e27dad ruby`sigsegv(sig=<unavailable>, info=<unavailable>, ctx=<unavailable>) at signal.c:955:5 frame #8: 0x00007f8b891d33c0 libpthread.so.0`___lldb_unnamed_symbol1$$libpthread.so.0 + 1 frame #9: 0x0000560763efa8bb ruby`rb_class_remove_from_super_subclasses(klass=94589790314280) at class.c:93:56 frame #10: 0x0000560763d10cb7 ruby`gc_sweep_step at gc.c:2674:2 frame #11: 0x0000560763d1187b ruby`gc_sweep at gc.c:4540:2 frame #12: 0x0000560763d101f0 ruby`gc_start at gc.c:6797:6 frame #13: 0x0000560763d15153 ruby`rb_gc_compact at gc.c:7479:12 frame #14: 0x0000560763eb4eb8 ruby`vm_exec_core at vm_insnhelper.c:5183:13 frame #15: 0x0000560763ea9bae ruby`rb_vm_exec at vm.c:1953:22 frame #16: 0x0000560763eac08d ruby`rb_yield at vm.c:1132:9 frame #17: 0x0000560763edb4f2 ruby`rb_ary_collect at array.c:3186:9 frame #18: 0x0000560763e9ee15 ruby`vm_call_cfunc_with_frame at vm_insnhelper.c:2575:12 frame #19: 0x0000560763eb2e66 ruby`vm_exec_core at vm_insnhelper.c:4177:11 frame #20: 0x0000560763ea9bae ruby`rb_vm_exec at vm.c:1953:22 frame #21: 0x0000560763eac08d ruby`rb_yield at vm.c:1132:9 frame #22: 0x0000560763edb4f2 ruby`rb_ary_collect at array.c:3186:9 frame #23: 0x0000560763e9ee15 ruby`vm_call_cfunc_with_frame at vm_insnhelper.c:2575:12 frame #24: 0x0000560763eb2e66 ruby`vm_exec_core at vm_insnhelper.c:4177:11 frame #25: 0x0000560763ea9bae ruby`rb_vm_exec at vm.c:1953:22 frame #26: 0x0000560763ceee01 ruby`rb_ec_exec_node(ec=0x0000560765afa530, n=0x0000560765b088e0) at eval.c:296:2 frame #27: 0x0000560763cf3b7b ruby`ruby_run_node(n=0x0000560765b088e0) at eval.c:354:12 frame #28: 0x0000560763cee4a3 ruby`main(argc=<unavailable>, argv=<unavailable>) at main.c:50:9 frame #29: 0x00007f8b88e560b3 libc.so.6`__libc_start_main + 243 frame #30: 0x0000560763cee4ee ruby`_start + 46 (lldb) f 9 frame #9: 0x0000560763efa8bb ruby`rb_class_remove_from_super_subclasses(klass=94589790314280) at class.c:93:56 90 91 *RCLASS_EXT(klass)->parent_subclasses = entry->next; 92 if (entry->next) { -> 93 RCLASS_EXT(entry->next->klass)->parent_subclasses = RCLASS_EXT(klass)->parent_subclasses; 94 } 95 xfree(entry); 96 } (lldb) command script import -r misc/lldb_cruby.py lldb scripts for ruby has been installed. (lldb) rp entry->next->klass (struct RMoved) $1 = (flags = 30, destination = 94589792806680, next = 94589784369160) (lldb) ```
* Update NEWS / documentation with GC.start(compact:true)Aaron Patterson2020-05-291-0/+8
|
* Added entries about RubyGems and BundlerHiroshi SHIBATA2020-05-251-0/+8
|
* NEWS.md: the order of backtrace [Feature #8661] [ci skip]Nobuyoshi Nakada2020-04-211-0/+5
|
* Fix a typo [ci skip]Kazuhiro NISHIYAMA2020-04-171-1/+1
|
* NEWS.md: Mentioned the removal of NIL/TRUE/FALSE [ci skip]Nobuyoshi Nakada2020-04-171-0/+2
|
* Raise EPIPE at broken pipe for the backward compatibilityNobuyoshi Nakada2020-04-151-3/+2
| | | | | | Instead of SignalException for SIGPIPE, raise `Errno::EPIPE` with instance variable `signo` and re-send that signal at exit. [Feature #14413]
* View the help message with PAGER [Feature #16754]Nobuyoshi Nakada2020-04-121-0/+8
| | | | | View the help message wth pager designed by RUBY_PAGER or PAGER environment variable, unless that value is empty.
* Silence broken pipe error messages on STDOUT [Feature #14413]Nobuyoshi Nakada2020-04-111-0/+5
| | | | Raise `SignalException` for SIGPIPE to abort when EPIPE occurs.
* Reference to [Feature #16746] [ci skip]Nobuyoshi Nakada2020-04-101-0/+1
|
* Endless method definition [Feature #16746]Nobuyoshi Nakada2020-04-101-0/+7
|
* R-assign is still experimental [Feature #15921] [ci skip]Nobuyoshi Nakada2020-04-101-1/+2
|
* Rightward-assign by ASSOCNobuyoshi Nakada2020-04-101-0/+7
| | | | [Feature #15921]
* Merge pull request #2991 from shyouhei/ruby.h卜部昌平2020-04-081-0/+4
| | | Split ruby.h
* Added link to the ticket [ci skip]Kazuhiro NISHIYAMA2020-03-181-0/+1
|
* Reduce allocations for keyword argument hashesJeremy Evans2020-03-171-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, passing a keyword splat to a method always allocated a hash on the caller side, and accepting arbitrary keywords in a method allocated a separate hash on the callee side. Passing explicit keywords to a method that accepted a keyword splat did not allocate a hash on the caller side, but resulted in two hashes allocated on the callee side. This commit makes passing a single keyword splat to a method not allocate a hash on the caller side. Passing multiple keyword splats or a mix of explicit keywords and a keyword splat still generates a hash on the caller side. On the callee side, if arbitrary keywords are not accepted, it does not allocate a hash. If arbitrary keywords are accepted, it will allocate a hash, but this commit uses a callinfo flag to indicate whether the caller already allocated a hash, and if so, the callee can use the passed hash without duplicating it. So this commit should make it so that a maximum of a single hash is allocated during method calls. To set the callinfo flag appropriately, method call argument compilation checks if only a single keyword splat is given. If only one keyword splat is given, the VM_CALL_KW_SPLAT_MUT callinfo flag is not set, since in that case the keyword splat is passed directly and not mutable. If more than one splat is used, a new hash needs to be generated on the caller side, and in that case the callinfo flag is set, indicating the keyword splat is mutable by the callee. In compile_hash, used for both hash and keyword argument compilation, if compiling keyword arguments and only a single keyword splat is used, pass the argument directly. On the caller side, in vm_args.c, the callinfo flag needs to be recognized and handled. Because the keyword splat argument may not be a hash, it needs to be converted to a hash first if not. Then, unless the callinfo flag is set, the hash needs to be duplicated. The temporary copy of the callinfo flag, kw_flag, is updated if a hash was duplicated, to prevent the need to duplicate it again. If we are converting to a hash or duplicating a hash, we need to update the argument array, which can including duplicating the positional splat array if one was passed. CALLER_SETUP_ARG and a couple other places needs to be modified to handle similar issues for other types of calls. This includes fairly comprehensive tests for different ways keywords are handled internally, checking that you get equal results but that keyword splats on the caller side result in distinct objects for keyword rest parameters. Included are benchmarks for keyword argument calls. Brief results when compiled without optimization: def kw(a: 1) a end def kws(**kw) kw end h = {a: 1} kw(a: 1) # about same kw(**h) # 2.37x faster kws(a: 1) # 1.30x faster kws(**h) # 2.19x faster kw(a: 1, **h) # 1.03x slower kw(**h, **h) # about same kws(a: 1, **h) # 1.16x faster kws(**h, **h) # 1.14x faster