Ruby

Expose IO::Buffer mapping alignment. (#18474)

[Feature #21700]

Hash::[] start from a right-sized hash

Saves on potentially having to reallocate multiple times.

Respect frozen IO::Buffer lifecycle state. (#18473)

[Bug #22219]

Validate IO::Buffer constructor flags. (#18470)

[Bug #21672]

Front-load slower compilation shards

Start slower and less predictable shards earlier to reduce the overall
workflow completion time.

Document IO::Buffer#free empty state. (#18471)

[Bug #22195]

Clarify IO::Buffer slice validity documentation. (#18469)

Process.warmup: recompute allocatable_bytes

A problem I ran into in production, is that the boot sequence,
which tend to be allocation heavy, would cause the allocatable_bytes
(or previous version equivalent) to grow much higher than what the
application runtime actually needs....

Avoid unsafe zero-length IO::Buffer operations. (#18465)

• All null? buffers will result in zero-length operations.

[ruby/rubygems] Note that the patch level options also imply strict

They flip the same strict flag as --filter-strict, so the cooldown
caveat applies to them too. Review finding UX-1 (round 3).

https://github.com/ruby/rubygems/commit/92933f7b7b

Co-Authored-By: Claude Fable 5 noreply@anthropic.com