ruby.git/iseq.c, branch v4.0.2 The Ruby Programming Language Remove assertion in encoded_iseq_trace_instrument (#15616) 2025-12-18T18:51:33+00:00 Luke Gruber luke.gruber@shopify.com 2025-12-18T18:51:33+00:00 74bfb1606d09672a37105c138edf8e0d8acbb5c1 `encoded_iseq_trace_instrument` is safe to call in a ractor if the iseq is new. In that case, the VM lock is not taken. This assertion was added in 4fb537b1ee28bb37dbe551ac65c279d436c756bc. 
`encoded_iseq_trace_instrument` is safe to call in a ractor if the iseq
is new. In that case, the VM lock is not taken. This assertion was added in
4fb537b1ee28bb37dbe551ac65c279d436c756bc.
 refactor: utilize a predefined macro 2025-12-17T03:37:13+00:00 Yusuke Endoh mame@ruby-lang.org 2025-12-17T02:57:57+00:00 e354e9ba1007c10df3ee843bb9daabd89b47a708 






Make tracepoints with set_trace_func or TracePoint.new ractor local (#15468)
2025-12-16T19:06:55+00:00

Luke Gruber
luke.gruber@shopify.com

2025-12-16T19:06:55+00:00

4fb537b1ee28bb37dbe551ac65c279d436c756bc

Before this change, GC'ing any Ractor object caused you to lose all
enabled tracepoints across all ractors (even main). Now tracepoints are
ractor-local and this doesn't happen. Internal events are still global.

Fixes [Bug #19112]




Before this change, GC'ing any Ractor object caused you to lose all
enabled tracepoints across all ractors (even main). Now tracepoints are
ractor-local and this doesn't happen. Internal events are still global.

Fixes [Bug #19112]






Binding#implicit_parameters, etc. support the implicit "it" parameter
2025-12-12T14:24:50+00:00

Yusuke Endoh
mame@ruby-lang.org

2025-12-12T07:43:25+00:00

129d74c96b0b8f1b93704b34e66d2c18f4835e1b

[Bug #21049]





[Bug #21049]







[DOC] Fix backticks in InstructionSequence docs
2025-11-29T01:43:26+00:00

Peter Zhu
peter@peterzhu.ca

2025-11-29T01:39:24+00:00

0f80d0ee05a2cb9daad426a7aa9aad7c4f2c3401












renaming internal data structures and functions from namespace to box
2025-11-07T04:14:54+00:00

Satoshi Tagomori
s-tagomori@sakura.ad.jp

2025-11-05T07:09:45+00:00

d2a587c79156275f66035d60bcc69882be61a3e1












fix ibf and coverage sharable issue
2025-10-30T09:04:08+00:00

Koichi Sasada
ko1@atdot.net

2025-10-30T07:21:33+00:00

ef558ceaefb91a55e97a8b5766e0643d0dcd078e












skip jit payload
2025-10-23T04:08:26+00:00

Koichi Sasada
ko1@atdot.net

2025-10-21T20:10:15+00:00

3b190855ba965c179693a5baf25f365d9d445c09

They should be checked, but not sure JIT code...





They should be checked, but not sure JIT code...







use `SET_SHAREABLE`
2025-10-23T04:08:26+00:00

Koichi Sasada
ko1@atdot.net

2025-09-24T20:50:05+00:00

bc00c4468e0054ca896d2b83d3020180915f64cf

to adopt strict shareable rule.

* (basically) shareable objects only refer shareable objects
* (exception) shareable objects can refere unshareable objects
  but should not leak reference to unshareable objects to Ruby world





to adopt strict shareable rule.

* (basically) shareable objects only refer shareable objects
* (exception) shareable objects can refere unshareable objects
  but should not leak reference to unshareable objects to Ruby world







Update Namespace#eval to use control frames instead of namespace_push/pop
2025-09-28T16:15:38+00:00

Satoshi Tagomori
s-tagomori@sakura.ad.jp

2025-08-10T09:45:44+00:00

32f58628e900894b48b9e8630c250dedbbb1c126

With this change, the argument code of Namespace#eval cannot refer local
variables around the calling line, but it should not be able to refer
these values. The code is evaluated in the receiver namespace, independently
from the local context.





With this change, the argument code of Namespace#eval cannot refer local
variables around the calling line, but it should not be able to refer
these values. The code is evaluated in the receiver namespace, independently
from the local context.