Age | Commit message (Collapse) | Author |
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3782
|
|
JunichiIto on GitHub correctly pointed out this is no longer
accurate due to the change to not display deprecation warnings by
default.
|
|
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3756
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3742
|
|
|
|
|
|
|
|
I'm sorry, but I think there is a typo here.
This fix will help folks who are trying to translate this announcement to other languages. I hope this is not a joke and I didn't get it 🙏
Notes:
Merged: https://github.com/ruby/ruby/pull/3730
|
|
* `GC.auto_compact=`, `GC.auto_compact` can be used to control when
compaction runs. Setting `auto_compact=` to true will cause
compaction to occurr duing major collections. At the moment,
compaction adds significant overhead to major collections, so please
test first!
[Feature #17176]
|
|
|
|
Setting this to true disables the deadlock detector. It should
only be used in cases where the deadlock could be broken via some
external means, such as via a signal.
Now that $SAFE is no longer used, replace the safe_level_ VM flag
with ignore_deadlock for storing the setting.
Fixes [Bug #13768]
Notes:
Merged: https://github.com/ruby/ruby/pull/3710
Merged-By: jeremyevans <code@jeremyevans.net>
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3674
|
|
|
|
|
|
Patch adapted from Pietro Monteiro [Fixes bug#8382]
Notes:
Merged: https://github.com/ruby/ruby/pull/3593
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3593
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3593
|
|
|
|
|
|
Matz want to try to freeze all Range objects.
[Feature #15504]
Notes:
Merged: https://github.com/ruby/ruby/pull/3583
|
|
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]]
|
|
Notes:
Merged-By: soutaro <matsumoto@soutaro.com>
|
|
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3562
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3561
|
|
|
|
|
|
* Remove freezestring instruction since this was the only usage for it.
* [Feature #17104]
Notes:
Merged: https://github.com/ruby/ruby/pull/3488
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/3540
|
|
|
|
|
|
Start with https://github.com/ruby/ruby/commit/fa21985a7a2f8f52a8bd82bd12a724e9dca74934
to https://github.com/ruby/ruby/commit/d7492a0be885ea9f2b9f71e3e95582f9a859c439
|
|
|
|
https://bugs.ruby-lang.org/issues/16150#change-87446
Notes:
Merged: https://github.com/ruby/ruby/pull/3514
Merged-By: nobu <nobu@ruby-lang.org>
|
|
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>
Notes:
Merged: https://github.com/ruby/ruby/pull/3418
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
asked by ko1 to put this.
|
|
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)
|