ruby.git/ruby.c, branch v3_3_11 The Ruby Programming Language merge revision(s) d33e3d47b84a73b38644f2a3d41881ce9be6ef18: [Backport #20704] 2024-11-04T22:36:36+00:00 Takashi Kokubun takashikkbn@gmail.com 2024-11-04T22:36:36+00:00 2b713dcb89c620daa55d672d2933ffde333ca5de [Bug #20704] Win32: Fix chdir to non-ASCII path On Windows, `chdir` in compilers' runtime libraries uses the active code page, but command line arguments in ruby are always UTF-8, since commit:33ea2646b98adb49ae2e1781753bf22d33729ac0. 
	[Bug #20704] Win32: Fix chdir to non-ASCII path

	On Windows, `chdir` in compilers' runtime libraries uses the active
	code page, but command line arguments in ruby are always UTF-8, since
	commit:33ea2646b98adb49ae2e1781753bf22d33729ac0.
merge revision(s) 01b13886: [Backport #20562] 2024-07-08T22:42:06+00:00 Takashi Kokubun takashikkbn@gmail.com 2024-07-08T22:42:06+00:00 a40645e115e6cd6328bb302dfc78b16f6ad45938 [Bug #20562] Categorize `RUBY_FREE_AT_EXIT` warning as experimental 
	[Bug #20562] Categorize `RUBY_FREE_AT_EXIT` warning as experimental
[Bug #20270] Fix --parser=prism (#10970) 2024-06-11T23:43:32+00:00 Peter Zhu peter@peterzhu.ca 2024-06-11T23:43:32+00:00 97b1bf9ac11848c2783264d22bf7cdb7f32a21cf Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com> 
Co-authored-by: Takashi Kokubun <takashikkbn@gmail.com>
 Don't add `+YJIT` to `RUBY_DESCRIPTION` until it's actually enabled (#10920) 2024-06-05T21:54:24+00:00 Jean byroot Boussier jean.boussier+github@shopify.com 2024-06-05T21:54:24+00:00 d0327a7224d8d778a75c7554b287369895dc17be If you start Ruby with `--yjit-disable`, the `+YJIT` shouldn't be added until `RubyVM::YJIT.enable` is actually called. Otherwise it's confusing in crash reports etc. Co-authored-by: Jean Boussier <jean.boussier@gmail.com> 
If you start Ruby with `--yjit-disable`, the `+YJIT` shouldn't be
added until `RubyVM::YJIT.enable` is actually called. Otherwise
it's confusing in crash reports etc.

Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
 RJIT: Add --rjit-trace to allow TracePoint during JIT 2023-12-22T05:05:13+00:00 Takashi Kokubun takashikkbn@gmail.com 2023-12-22T04:57:34+00:00 64c52cd1c2df840a021dd952b42bddde09534b1b 






Correct free_on_exit env var to free_at_exit
2023-12-20T05:36:32+00:00

HParker
HParker@github.com

2023-12-20T05:12:18+00:00

7ef90b3978dad057ad6360a94d2d64e8ca5e9c38












We need to load builtins so that they work
2023-12-19T16:53:52+00:00

Aaron Patterson
tenderlove@ruby-lang.org

2023-12-18T23:16:31+00:00

df0bfde2b29b7e8dac333b2a775ab8bff1283a5c

Before this commit no methods defined in Ruby were being loaded. For
example `class` or `tap` methods would not exist.

[ruby-core:115793] [Bug #20073]





Before this commit no methods defined in Ruby were being loaded. For
example `class` or `tap` methods would not exist.

[ruby-core:115793] [Bug #20073]







[PRISM] Fix crash when --parser=prism called with stdin
2023-12-18T19:44:44+00:00

Matt Valentine-House
matt@eightbitraptor.com

2023-12-18T16:56:01+00:00

893fe30ef2b30525d932d6b1256f717cc60b3311

[Bug #20071]

Currently Ruby crashes when the --parser=prism flag is used either with
no input, or with input that is being redirected from stdin. So all of
the following will crash

ruby --parser=prism
ruby --parser=prism < test_code.rb
cat test_code.rb | ruby --parser=prism

This commit checks whether the input is assumed to be from stdin, and
then processes that as a file.

This will fix the second and third case above, but will cause a slight
behavioural changes for the first case - Ruby will treat stdin as an
empty file in this case and exit, rather than waiting for data to be
piped into stdin.





[Bug #20071]

Currently Ruby crashes when the --parser=prism flag is used either with
no input, or with input that is being redirected from stdin. So all of
the following will crash

ruby --parser=prism
ruby --parser=prism < test_code.rb
cat test_code.rb | ruby --parser=prism

This commit checks whether the input is assumed to be from stdin, and
then processes that as a file.

This will fix the second and third case above, but will cause a slight
behavioural changes for the first case - Ruby will treat stdin as an
empty file in this case and exit, rather than waiting for data to be
piped into stdin.







Adjust styles [ci skip]
2023-12-16T15:21:00+00:00

Nobuyoshi Nakada
nobu@ruby-lang.org

2023-12-16T15:21:00+00:00

2f595c744e10f7d5222c477efd50fe168fe9d47e












update message to clarify compiler, not parser
2023-12-15T18:42:19+00:00

Adam Hess
HParker@github.com

2023-12-14T22:40:37+00:00

a604fe42620735f7bd1145e01bdca5398231ffb0

Co-authored-by: Ufuk Kayserilioglu <ufuk@paralaus.com>




Co-authored-by: Ufuk Kayserilioglu <ufuk@paralaus.com>