Activity
From 12/29/2025 to 01/04/2026
Today
-
03:53 AM Revision ca0fece5 (git): [DOC] Tweak an example in language/box.md
- Although the example code comments indicate that it returns `false`,
a non-matching result for `=~` is actually `nil`.
```ruby
Foo.foo.blank? #=> false
"foo".blank? #=> false
```
https://github.com/ruby/ruby/blob/v4.0.0-preview3/doc/... -
- Based on the example, it appears that `foo.rb` and `main.rb` are expected to be in the same directory.
Since Ruby 1.9, the current directory is not included in `$LOAD_PATH` by default.
As a result, running `box.require('foo')` as shown i... -
01:26 AM Revision 5064af7e (git): [ruby/mmtk] Process obj_free candidates in parallel
- Redos commit 544770d which seems to have accidentally been undone in b27d935.
01/03/2026
-
07:58 PM Misc #21777: DevMeeting-2026-01-14
- * [Feature #21264] Extract Date library from Ruby repo in the future (jeremyevans0)
* Do we want to extract `date` to bundled gems?
* I'm fine keeping it as stdlib, and if it needs a maintainer, I volunteer to maintain it.
* If ... -
09:22 AM Misc #21777: DevMeeting-2026-01-14
- * [Feature #21800] `Dir.foreach` and `Dir.each_child` to optionally yield `File::Stat` object alongside the children name (byroot)
* It's common for development tools to need to recursively scan the file system, but it's slower than i... -
- I've been thinking more about this. If we want to move `date` from stdlib to bundled gems, I still think it would be best to have a subset of the current `Date` as be a core class. `Date` is very widely used, but the vast majority of usa...
-
- I have another PR that allow Backtrace objects to be duped, hence to send them across Ractors: https://github.com/ruby/ruby/pull/15795
-
- > I'm not sure if there is a way to allow an object to be copied without defining an allocator function.
So I experimented with this a bit. It wouldn't be hard at all to disable `Class#allocate` while still allowing `rb_obj_dup` etc t... -
- > https://github.com/ruby/ruby/pull/15790 fixes the make_shareable.
Actually, might be more tricky than that. `Backtrace` object have two lazily instantiated mutable arrays (`backtrace` and `backtrace_locations`). So if we mark them ... -
-
-
10:11 AM Feature #21822 (Open): Expose Return Value in the ensure Block
I'd like to propose a simple feature that allows easy access to the return value inside an ensure block.
```ruby
begin
# ...
ensure => ret
# ret is nil if an exception is raised
LOGGER.debug "return value: #{ret}"
en...-
- > I think it will depend on what you achieve with Stack.
Yes, the point is to use it in cases where synchronization is needed, hence Array is not suitable. Typically connection pools: https://github.com/mperham/connection_pool/blob/8b... -
09:35 AM Feature #21821: Add Stack and SizedStack classes
- byroot (Jean Boussier) wrote:
> Currently `Queue` and `SizedQueue` are technically defined under `Thread` and aliased in `Object`.
> ...
I think it will depend on what you achieve with `Stack`.
If you want to use it for inter thread... -
- ### Context
`Queue` and `SizedQueue` are very useful and performant constructs, however they only allow for FIFO queues.
Some use cases do call for LIFO queues AKA stacks.
For instance, in the case of connection pool, it's often p... -
09:12 AM Revision 65f9c4a0 (git): Drop memberless Data/Struct#inspect trailing space
- Anonymous memberless Structs and Data were returning `#<struct >` and
`#<data >` with a trailing space. Now they return `#<struct>` and
`#<data>` to match attrless class behavior and look a bit more compact. -
- > the point is MonitorMixin seems well done and core-worthy.
Yeah, I don't think I agree with this. I never use it because including it expose a bunch of `mon_*` public methods that nobody ever use.
At the end of the day 99% of Monit... - 08:30 AM Revision b6463d59 (git): [ruby/json] Directly write to the output buffer when converting UTF32 to UTF8.
- https://github.com/ruby/json/commit/a51317c949
-
- Applied in changeset commit:git|d7a6ff8224519005d2deeb3f4e98689a8a0835ad.
----------
[Bug #21819] Data objects without members should also be frozen -
- [GH-15792](https://github.com/ruby/ruby/pull/15792)
-
02:19 AM Bug #21819 (Closed): A Data object should be frozen even if it has no members
- Data objects with at least one member are currently automatically frozen on construction, and shareable if all members are shareable. However, a Data object with no members is not frozen on construction. I would expect such an object sim...
-
-
- Delete test/net/imap/test_data_lite.rb, because the target of this
test file has been deleted by [ruby/net-imap#543].
[ruby/net-imap#543]: https://github.com/ruby/net-imap/pull/593 -
03:20 AM Bug #21820 (Open): "vm_call_cfunc: cfp consistency error" occurs during rdoc generation when installing Ruby 4.0.0 via rbenv on Ubuntu 24.04
- This is transferred from https://github.com/rbenv/ruby-build/discussions/2594#discussioncomment-15394211
# My environment
``` shell
[sue445@sue445-win] [12-31 23:34:49] $ lsb_release -a
No LSB modules are available.
Distributor ID... -
- https://github.com/ruby/mmtk/commit/308936296a
-
- This allows the mutator thread to dump its backtrace when a GC thread crashes.
https://github.com/ruby/mmtk/commit/40ff9ffee7
01/02/2026
-
- A large part of `thread_sync.c` was migrated already, might as well
go all the way. It also allow to remove a bunch of Rdoc commands. -
- https://github.com/ruby/ruby/pull/15790 fixes the `make_shareable`. As for sending, I'm not sure if there is a way to allow an object to be copied without defining an allocator function.
-
- > Is this intentional?
I don't think so, more of an oversight. Looking at the implementation, I don't see a reason why it couldn't be marked as FROZEN_SHAREABLE. -
- It looks like Thread::Backtrace is confined to the Ractor that produced it: it cannot be copied or moved to another Ractor, nor can it be made shareable. This makes it difficult for a Ractor to communicate exceptions (e.g. the reason for...
-
- https://github.com/ruby/mmtk/commit/c3e338bb25
-
- https://github.com/ruby/mmtk/commit/58210c88ed
-
- Using `eval` it's possible to reference a later argument, and
this requires careful initialization of the stack. -
- They are optional because they have a default value, so I don't
understand why we'd need to initialize them to nil. -
-
- Rather than to push items one by one we can directly memcpy.
- 08:43 AM Revision 11165495 (git): [ruby/rubygems] Bump the rb-sys group across 2 directories with 1 update
- Bumps the rb-sys group with 1 update in the /test/rubygems/test_gem_ext_cargo_builder/custom_name/ext/custom_name_lib directory: [rb-sys](https://github.com/oxidize-rb/rb-sys).
Bumps the rb-sys group with 1 update in the /test/rubygems/t... - 06:55 AM Revision 0ec5678c (git): Update bundled gems list as of 2026-01-02
-
- The version message may contain other info such as the distribution.
e.g.:
```console
$ /usr/bin/git --version
git version 2.50.1 (Apple Git-155)
``` -
-
01/01/2026
-
- https://github.com/ruby/mmtk/commit/42adba630e
-
12:30 PM Revision 26a5bcd6 (git): [ruby/prism] Fix spacing in the generated #each_child_node
- https://github.com/ruby/prism/commit/91f60cb736
-
- Thread::Queue spends a significant amount of time in array functions,
checking for invariants we know aren't a problem, and whether the backing
array need to reordered.
By using a ring buffer we can remove a lot of overhead (~23% faster... -
- str_duplicate_setup_heap is missing a call to rb_gc_register_pinning_obj
that STR_SET_SHARED correctly calls. -
12/31/2025
-
11:49 PM Bug #21817 (Assigned): Ruby::Box crashes with refinement + bind_call + Symbol#to_proc combination
- ## Description
When running with `RUBY_BOX=1`, a combination of refinement on Binding class, `bind_call`, and `Symbol#to_proc` causes a crash with the error: `[BUG] BUG: Local ep without cme/box, flags: 66660087`
## Reproduction ... -
- It sometimes pins itself when it is in the overloaded_cme table.
-
- The argument to `is_data_encoding` is assumed to be `T_DATA`.
-
- This makes it easier to visualize in profilers which one is non-parallel.
https://github.com/ruby/mmtk/commit/ba68b2ef3b -
- This commit allows objects that are safe to be freed in parallel to do so.
A decrease in object freeing time can be seen in profiles.
The benchmarks don't show much difference.
Before:
-------------- -------------------- ---------- ... -
- A plain `char` may be `signed` or `unsigned` depending on the
implementation. Also, bitwise ORing of `signed` values is not
guaranteed to be `signed`. To ensure portability, should logical-OR
each comparison, but casting to `signed c... -
-
- Alright. I'll close this for now, and consider opening a feature request for `Thread::Stack`.
- 10:07 AM Revision c97f5d59 (git): [ruby/json] Simplify unescape_unicode
- https://github.com/ruby/json/commit/976ba36629
Co-Authored-By: Jean Boussier <jean.boussier@gmail.com> - 09:54 AM Revision 61d45c85 (git): [ruby/json] Keep track of the the number of additional backslashes to avoid an extra memchr searching the remaining characters when no more backslashes exist.
- https://github.com/ruby/json/commit/d21d9362fa
-
- The flags for `rb_data_type_t::flags` are public constants for
defining `rb_data_type_t`. The embedded data flag and mask are
internal implementation detail. -
- matz (Yukihiro Matsumoto) wrote in #note-35:
> I still do not see enough benefit in putting in incompatible changes. Even if we can rewrite all the gems, we will still have incompatibility issues in user applications.
It seems extrem... -
03:33 AM Feature #8948: Frozen regex
- Eregon (Benoit Daloze) wrote in #note-34:
> @matz Is it OK to merge https://github.com/ruby/ruby/pull/14547 now for 4.1?
I still do not see enough benefit in putting in incompatible changes. Even if we can rewrite all the gems, we wi... -
- Probably it's because of commit:c970d2941d56a862bb9bb3b808cb588c2982f436.
That is the indent is not related, but the behavior change. -
03:53 AM Bug #21816 (Open): iseq code_location of proc changed
- TBH, I'm not really sure if that title matches the problem here, but I can produce this issue with the following test:
```ruby
# bug.rb
# note the indentation of the callable
callable = -> { puts "Hello, World!" }
iseq = Rub... -
- It should not be exposed because it is so implementation specific that
it is only used in gc.c even within the entire Ruby source tree. -
- The combination of `&` and `&&` is confusing.
12/30/2025
-
09:44 PM Misc #21804: Getting setup-ruby Earlier
- I left some thoughts in the PR, but will post here to keep discussion in one place.
> Thanks for taking the time to open this PR to move the discussion forward, even though you’re understandably skeptical of the approach. I share your... -
- Earlopain (Earlopain _) wrote in #note-6:
> But I think the bigger issue here is that windows builds are not first-party. So even if the release process gets adapted, issues like what [@mdalessio (Mike Dalessio)](/users/443) wrote above... -
- Eregon (Benoit Daloze) wrote in #note-2:
> So I think this is something to add to the post-release checklist:
@hsbt Would you be willing to do those steps when releasing a new version? Is there a public release checklist somewhere?
Othe... -
- Earlopain (Earlopain _) wrote in #note-6:
> I don't really see the point of automerging PRs when someone still has to create the release manually. Merging the PRs is not much effort, someone just needs to do it.
I meant the release w... -
07:58 PM Misc #21804: Getting setup-ruby Earlier
- I don't really see the point of automerging PRs when someone still has to create the release manually. Merging the PRs is not much effort, someone just needs to do it.
Having this happen as part of release management sounds reasonable... -
03:51 PM Misc #21804: Getting setup-ruby Earlier
- > Maybe it'd make sense and possibly safe enough to automatically merge PRs by ruby-builder-bot, after they pass CI of course ... if someone is interested, please make a PR to setup-ruby.
I've opened https://github.com/ruby/setup-ruby... -
> https://github.com/ruby/setup-ruby/pull/844 got merged the same day, what would you expect?
A counter-example, though, is that the PR for windows support (https://github.com/ruby/setup-ruby/pull/847) took 3 days to get merged.
I thi...-
- Maybe it'd make sense and possibly safe enough to automatically merge PRs by `ruby-builder-bot`, after they pass CI of course.
I'm not sure how feasible that is (e.g. is there a GHA event triggered when CI has passed?), but if someone is... -
- https://github.com/ruby/setup-ruby/pull/844 got merged the same day, what would you expect?
Concretely I currently merge setup-ruby PRs and I have told @hsbt in the past he can merge (+ release) for new added versions.
More people co... -
- * [Feature #8948] Frozen regex (eregon)
* Can we merge it now for 4.1? Then there is plenty of time for the few gems that rely on mutable Regexp to adapt.
* We can also revert it if it turns out to be too disrupting. -
- @matz Is it OK to merge https://github.com/ruby/ruby/pull/14547 now for 4.1?
Then there is plenty of time for the few gems that rely on mutable Regexp to adapt.
BTW I noticed someone else also did a PR for this, so there seems to be ... -
- https://github.com/ruby/mmtk/commit/290a2aec4e
-
-
-
-
- Thanks, good find! I have a fix here: https://github.com/ruby/ruby/pull/15772
-
05:44 AM Feature #21084 (Open): Declare objects have weak references
- I don't think this works correctly with generational GC. This crashes reliably on HEAD (works fine on 4.0.0)
``` ruby
wmap = ObjectSpace::WeakMap.new
GC.disable # only manual GCs
GC.start
GC.start
retain = []
50.times do
... -
-
- Fixes issue pointed out in https://bugs.ruby-lang.org/issues/21084#note-7.
The following script crashes:
wmap = ObjectSpace::WeakMap.new
GC.disable # only manual GCs
GC.start
GC.start
retain = []
50.times do
... -
- Applied in changeset commit:git|c970d2941d56a862bb9bb3b808cb588c2982f436.
----------
[Bug #21784] Fix the Proc#source_location start_column for stabby lambdas
* Consistent with plain `blocks` and `for` blocks and methods
where the so... -
- Applied in changeset commit:git|cd66d15858a06406d1de854f3e9690d3557a9864.
----------
[Bug #21783] Fix documentation of {Method,UnboundMethod,Proc}#source_location -
- Applied in changeset commit:git|d82fc3360d7cfa7e1e1a4dddb668b4c38808538a.
----------
Reapply "[Feature #6012] Extend `source_location` for end position
* This reverts commit 065c48cdf11a1c4cece84db44ed8624d294f8fd5.
* This functionalit... -
- * See https://github.com/ruby/ruby/pull/15580
-
-
- * Consistent with plain `blocks` and `for` blocks and methods
where the source_location covers their entire definition.
* Matches the documentation which mentions
"where the definition starts/ends".
* Partially reverts d357d50f0a7440... -
-
- * This reverts commit 065c48cdf11a1c4cece84db44ed8624d294f8fd5.
* This functionality is very valuable and has already taken 14 years
to agree on the API.
* Let's just document it's byte columns (in the next commit).
* See https://bugs.... -
-
- [GH-15737] needs to be backported to the 4.0 branch.
[GH-15737]: https://github.com/ruby/ruby/pull/15737 -
- Applied in changeset commit:git|19e539c9ee1701b34189fa0c1feb942adeb0e326.
----------
[Bug #21814] Fix negative bignum modulo
If modulo is zero, do not apply bias even if the divisor is zero.
`BIGNUM_POSITIVE_P` is true even on bignum ... -
- [GH-15771](https://github.com/ruby/ruby/pull/15771)
-
- When I try `0.pow(2,-9999999999999999990)`, irb prints `-9999999999999999990`, but I think no matter what you divide zero by, the modulo should be zero.
Matz.
-
- If modulo is zero, do not apply bias even if the divisor is zero.
`BIGNUM_POSITIVE_P` is true even on bignum zero. - 01:31 PM Revision 966dbba8 (git): Box: skip checking the current box is the root box
- Because checking the current box is not a cheap process.
-
-
-
- This might be useful for `A`, `a`, and `Z` as well.
Updated the PR [GH-15647] to use `^` with the tests.
[GH-15647]: https://github.com/ruby/ruby/pull/15647 - 08:06 AM Revision d5af8d78 (git): Box: allocate classes as boxable when it happens in the root box
- Without this change, classes (including iclass) are allocated
as un-boxable classes after initializing user boxes (after starting
script evaluation). Under this situation, iclasses are created as
un-boxabled class when core modules are i... -
06:24 AM Feature #21797: Make Etc.nprocessors cgroup-aware on Linux
- Thank you for the summary!
I'll open a separate ticket for auto-adjusting `RUBY_MAX_CPU`.
Come to think of it, `RUBY_MAX_CPU` may have different requirements from `Etc.nprocessors` (defaulting to max # of processors may be suboptimal... -
12:22 AM Feature #21813 (Open): Add [:forward, :...] symbol tuple to indicate forwarding arguments when calling `Method#parameters`
- When accessing `Method#parameters` for a method using forwarding parameters, an unexpected behavior arises:
```ruby
def foo(*, **, &)
binding.eval "print(#{(method(__method__).parameters.dig(0,1))})" # Works fine
end
foo(1,2,3...
12/29/2025
-
04:42 PM Bug #21812 (Assigned): Kernel#sleep without arguments returns immediately when subprocess exits in another thread (regression in Ruby 4.0)
- Thanks for the nice catch.
`git bisect` points to commit:8d8159e7d87e4fd1594ce2fad3d2653e47fb1026. The changes in that commit seem relevant to this issue.
@luke-gru Could you take a look? -
04:12 PM Bug #21812 (Assigned): Kernel#sleep without arguments returns immediately when subprocess exits in another thread (regression in Ruby 4.0)
- **Description**
In Ruby 4.0.0, Kernel#sleep without arguments returns 0 immediately when a subprocess (spawned via backticks in another thread) exits. This is a regression from Ruby 3.4.8 where sleep blocks indefinitely as expected.
... -
- `compact_child_nodes` allocates an array. We can skip that step by simply yielding the nodes.
Benchmark for visiting the rails codebase:
```rb
require "prism"
require "benchmark/ips"
files = Dir.glob("../rails/**/*.rb")
results = file... -
02:12 PM Revision 14fbcf0e (git): [ruby/prism] Report missing end errors at opening token
- This commit adds an `expect1_opening` function that expects a token and
attaches the error to the opening token location rather than the current
position. This is useful for errors about missing closing tokens, where
we want to point to ... -
- https://github.com/ruby/prism/commit/166764f794
-
- This commit implements moving Immix in MMTk, which allows objects to move
in the GC.
The performance of this implementation is not yet amazing. It is very
similar to non-moving Immix in many of them and slightly slower in others.
The be... -
-
-
-
12:41 PM Bug #21801: compile failed at 4.0.0 preview 3 and snapshot issue
- It may be worth noting that the filename x64-msvcrt-ruby400.dll indicates the use of a 64-bit msvcrt.dll runtime environment.
When trying to build master in a 32-bit msvcrt environment, I encountered a similar issue.
While I cannot d... -
07:01 AM Bug #21801: compile failed at 4.0.0 preview 3 and snapshot issue
- nobu (Nobuyoshi Nakada) wrote in #note-2:
> darkspy (gerty ken) wrote:
> ...
now i tried cross compile from mingw64 in linux for windows target. the ruby 4 still can not run:
test.rb:
$stdout.sync = true
puts "test"
ruby test.rb
... -
- `ALLOCA` with too large size may result in stack overflow.
Incidentally, this suppresses the GCC false maybe-uninitialized
warning in `product_each`.
Also shrink `struct product_state` when `sizeof(int) < sizeof(VALUE)`. -
-
-
-
-
- https://github.com/ruby/ruby/pull/15763
- 08:21 AM Revision 4e0bb58a (git): fix underflow
-
05:54 AM Revision 38701a4d (git): Remove deprecated support for to_set taking arguments
-
05:03 AM Feature #21797: Make Etc.nprocessors cgroup-aware on Linux
- > What would be the value of nprocessor in this case?, e.g. if cpu_quotais 0.5, what does nprocessors return? cpu_quota.ceil?
I think it depends on the decision, but either floor or ceil should be fine (for reference, Go’s `GOMAXPROCS... -
- In public headers, casts should be enclosed in `RBIMPL_CAST` for
compilation in C++.