Skip to content

[pull] master from ruby:master#880

Merged
pull[bot] merged 14 commits intoturkdevops:masterfrom
ruby:master
Mar 24, 2026
Merged

[pull] master from ruby:master#880
pull[bot] merged 14 commits intoturkdevops:masterfrom
ruby:master

Conversation

@pull
Copy link
Copy Markdown

@pull pull bot commented Mar 24, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

byroot and others added 14 commits March 24, 2026 14:24
Currently there is just one very basic one.

ruby/prism@5a184b8085
They may not be part of `on_param` but ripper still calls `on_ident` for them

ruby/prism@fb5303f2b8
* The Loader API lives under java/api.
* The current native endpoint for the Prism shared library lives
  under java/native.
* The WASM build and binding lives under java/wasm.

The libraries will be released together but can be developed and
snapshotted independently. Users that copy the source from the
previous java/ will want to grab both java/api/src/main/java and
java/native/src/main/java contents.

ruby/prism@03358d5bcf
This uses the JRuby rake-maven-plugin to generate the templates
as part of the Maven build. The generated output for the Java
templates will be under java/api/target/generated-sources/java.

ruby/prism@b257151391
Callers should use the safer `RTYPEDDATA_GET_DATA`.
This helps distinguish an OutOfMemory (intended to be for running out of
code space) from a native frame needing too much stack space. On
protoboeuf, for example:

    Top-2 compile error reasons (100.0% of total 5,798,926):
               out_of_memory: 3,074,342 (53.0%)
      native_stack_too_large: 2,724,584 (47.0%)
We were accidentally marking OutOfMemory when actually the problem was
that the native stack was too big. Slightly re-think emit APIs to make
this mistake harder to make.

Now protoboeuf looks like this:

    Top-1 compile error reasons (100.0% of total 5,798,926):
      native_stack_too_large: 5,798,926 (100.0%)
Too-complex shapes use hash tables for ivar storage, and
rb_shape_get_iv_index() doesn't work for them (it asserts in debug
builds). Without this check, the polymorphic getinstancevariable
optimization incorrectly returns nil for ivars on too-complex objects.

Let the fallthrough GetIvar handle these shapes instead.
@pull pull bot locked and limited conversation to collaborators Mar 24, 2026
@pull pull bot added the ⤵️ pull label Mar 24, 2026
@pull pull bot merged commit e74823a into turkdevops:master Mar 24, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants