December 2024 - ruby-core - ml.ruby-lang.org

[ruby-core:120431] [Ruby master Bug#20988] String literal that includes `\C-` `\M-` with `\111` wrongly parsed
by tompng (tomoya ishida) 29 Dec '24

29 Dec '24

Issue #20988 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #20988: String literal that includes `\C-` `\M-` with `\111` wrongly parsed https://bugs.ruby-lang.org/issues/20988 * Author: tompng (tomoya ishida) * Status: Open * ruby -v: ruby 3.5.0dev (2024-12-27T07:27:30Z master adbbc9109e) +YJIT +MN +PRISM [arm64-darwin22] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Prism and parse.y parses this string literal differently. ~~~ $ ./ruby -e 'p "\C-\111 \M-\111 \M-\C-\111"' "I I I" ~~~ ~~~ $ ./ruby --parser=parse.y -e 'p "\C-\111 \M-\111 \M-\C-\111"' "\t \xC9 \x89" ~~~ -- https://bugs.ruby-lang.org/

2 1

[ruby-core:120437] [Ruby master Bug#20991] Prism parses `"\C-\α"` into `"α"` which should be syntax error
by tompng (tomoya ishida) 28 Dec '24

28 Dec '24

Issue #20991 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #20991: Prism parses `"\C-\α"` into `"α"` which should be syntax error https://bugs.ruby-lang.org/issues/20991 * Author: tompng (tomoya ishida) * Status: Open * ruby -v: ruby 3.5.0dev (2024-12-27T07:27:30Z master adbbc9109e) +YJIT +MN +PRISM [arm64-darwin22] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- ~~~ $ ./ruby -e 'p "\C-\α"' "α" ~~~ I think it should raise `Invalid escape character syntax` just like `"\C-α"` does. ~~~ruby "\C-α" # Invalid escape character syntax "\C-\α" # Prism: "α" # parse.y: invalid multibyte char (UTF-8), reported in #20990 ~~~ -- https://bugs.ruby-lang.org/

1 1

[ruby-core:120435] [Ruby master Bug#20990] Ripper.tokenize splits `"\C-\あ"` into tokens with invalid byte sequence
by tompng (tomoya ishida) 28 Dec '24

28 Dec '24

Issue #20990 has been reported by tompng (tomoya ishida). ---------------------------------------- Bug #20990: Ripper.tokenize splits `"\C-\あ"` into tokens with invalid byte sequence https://bugs.ruby-lang.org/issues/20990 * Author: tompng (tomoya ishida) * Status: Open * ruby -v: ruby 3.4.1 (2024-12-25 revision 48d4efcb85) +YJIT +MN [arm64-darwin22] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- IRB crashes when a code is tokenized to an invalid byte sequence. ~~~ruby Ripper.tokenize '"\C-\あ"' #=> ["\"", "\\C-\\\xE3\x81", "\x82", "\""] ~~~ I think the error evaluating `"\C-\あ"` should be `Invalid escape character syntax` just like `"\C-あ"` ~~~ $ ./ruby --parser=parse.y -e '"\C-あ"' -e:1: Invalid escape character syntax "\C-あ" $ ./ruby --parser=parse.y -e '"\C-\あ"' -e:1: invalid multibyte char (UTF-8) -e:1: invalid multibyte char (UTF-8) ./ruby: compile error (SyntaxError) ~~~ -- https://bugs.ruby-lang.org/

1 1

[ruby-core:119534] [Ruby master Bug#20800] Don't place `ruby` executable into `/usr/libexec/x86_64-linux/bin`
by vo.x (Vit Ondruch) 27 Dec '24

27 Dec '24

Issue #20800 has been reported by vo.x (Vit Ondruch). ---------------------------------------- Bug #20800: Don't place `ruby` executable into `/usr/libexec/x86_64-linux/bin` https://bugs.ruby-lang.org/issues/20800 * Author: vo.x (Vit Ondruch) * Status: Open * ruby -v: ruby 3.4.0dev (2024-10-15 master 3da3cabf98) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- Trying to prepare Ruby 3.4 package for Fedora, it seems that since [1], the `ruby` executable is installed into `/usr/libexec/x86_64-linux/bin`: ~~~ installing binary commands: /usr/libexec/x86_64-linux/bin ~~~ Unfortunately, the PR does not explain anything about reasons why. To me, using `libexec` is surprising, because according to FHS [2], the directory is for internal binaries. What is even more surprising is usage of the `bin` subdirectory there, which IMHO does not follow any standard or convention (I don't have `/usr/libexec/x86_64-linux/bin` directory on my Fedora yet). Just FTR, these are the configuration options used: ~~~ /builddir/build/BUILD/ruby-3.4.0_20241016git3da3cabf98-build/ruby-3.4.0-3da3cabf98/configure --build=x86_64-redhat-linux-gnu --host=x86_64-redhat-linux-gnu --program-prefix= --disable-dependency-tracking --prefix=/usr --exec-prefix=/usr --bindir=/usr/bin --sbindir=/usr/sbin --sysconfdir=/etc --datadir=/usr/share --includedir=/usr/include --libdir=/usr/lib64 --libexecdir=/usr/libexec --localstatedir=/var --runstatedir=/run --sharedstatedir=/var/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-rubylibprefix=/usr/share/ruby --with-archlibdir=/usr/lib64 --with-rubyarchprefix=/usr/lib64/ruby --with-sitedir=/usr/local/share/ruby/site_ruby --with-sitearchdir=/usr/local/lib64/ruby/site_ruby --with-vendordir=/usr/share/ruby/vendor_ruby --with-vendorarchdir=/usr/lib64/ruby/vendor_ruby --with-rubyhdrdir=/usr/include --with-rubyarchhdrdir=/usr/include '--with-sitearchhdrdir=$(sitehdrdir)/$(arch)' '--with-vendorarchhdrdir=$(vendorhdrdir)/$(arch)' --with-rubygemsdir=/usr/share/rubygems --with-ruby-pc=ruby.pc --with-compress-debug-sections=no --disable-rpath --enable-mkmf-verbose --enable-shared --with-ruby-version= --enable-multiarch --enable-yjit ~~~ The `--enable-multiarch` is among the options. It is used not because Fedora would be `multiarch`, but because it provides the highest flexibility. [1]: https://github.com/ruby/ruby/pull/10010 [2]: https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html -- https://bugs.ruby-lang.org/

4 9

[ruby-core:120423] [Ruby master Bug#20986] Bug in Prism parser with `?\C`
by tenderlovemaking (Aaron Patterson) 26 Dec '24

26 Dec '24

Issue #20986 has been reported by tenderlovemaking (Aaron Patterson). ---------------------------------------- Bug #20986: Bug in Prism parser with `?\C` https://bugs.ruby-lang.org/issues/20986 * Author: tenderlovemaking (Aaron Patterson) * Status: Open * Assignee: prism * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Prism output is this: ``` $ ./miniruby -e 'p ?\C-\]' "]" ``` Parse.y output is this: ``` $ ./miniruby --parser=parse.y -e 'p ?\C-\]' "\u001D" ``` -- https://bugs.ruby-lang.org/

3 2

[ruby-core:120147] [Ruby master Bug#20939] When using the parse.y parser, it occurs argument stack underflow (-1) if there is processing after the shareable_constant_value: experimental_everything comment and `C = { **{ k: v } }`
by ydah (Yudai Takada) 26 Dec '24

26 Dec '24

Issue #20939 has been reported by ydah (Yudai Takada). ---------------------------------------- Bug #20939: When using the parse.y parser, it occurs argument stack underflow (-1) if there is processing after the shareable_constant_value: experimental_everything comment and `C = { **{ k: v } }` https://bugs.ruby-lang.org/issues/20939 * Author: ydah (Yudai Takada) * Status: Open * ruby -v: ruby 3.4.0dev (2024-12-10T03:31:47Z master f12e2622c1) [arm64-darwin23] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- The following code will occurs argument stack underflow if it is a parse.y parser. ```ruby # shareable_constant_value: experimental_everything C = { **{ k: v } } p C ``` The following error message is output. ``` ruby 3.4.0dev (2024-12-06T03:32:20Z master 6ccaa37eb3) [arm64-darwin23] -- raw disasm-------- trace: 1 0000 putspecialobject 1 ( 2) 0002 putobject :k ( 2) 0004 putself ( 2) 0005 opt_send_without_block <calldata:v, 0> ( 2) 0007 newhash 2 ( 2) 0009 newhash 2 ( 2) 0011 opt_send_without_block <calldata:make_shareable, 1> ( 2) 0013 putspecialobject 3 ( 2) * 0015 setconstant :C ( 2) trace: 1 0017 putself ( 3) 0018 opt_getconstant_path [:C] ( 3) 0020 opt_send_without_block <calldata:p, 1> ( 3) 0022 leave ( 3) --------------------- -e:2: argument stack underflow (-1) -e: compile error (SyntaxError) ``` It does not occur in the following cases: ```ruby # shareable_constant_value: experimental_everything C = { **{ k: v } } ``` ```ruby C = { **{ k: v } } p C ``` ```ruby # shareable_constant_value: experimental_everything { **{ k: v } } p C ``` ```ruby # shareable_constant_value: experimental_everything C = { **{ k: 1 } } p C ``` This does not occur in Ruby 3.3: ``` ❯ ruby --parser=parse.y -v -e '# shareable_constant_value: experimental_everything C = { **{ foo: bar } } p C' ruby 3.3.6 (2024-11-05 revision 75015d4c1f) [arm64-darwin23] -e:3:in `<main>': undefined local variable or method `bar' for main (NameError) C = { **{ foo: bar } } ^^^ ``` -- https://bugs.ruby-lang.org/

2 2

[ruby-core:118182] [Ruby master Bug#20526] File.open(encoding: "bom|utf-8") converts "\r\n" to "\n" on Windows
by kou (Kouhei Sutou) 26 Dec '24

26 Dec '24

Issue #20526 has been reported by kou (Kouhei Sutou). ---------------------------------------- Bug #20526: File.open(encoding: "bom|utf-8") converts "\r\n" to "\n" on Windows https://bugs.ruby-lang.org/issues/20526 * Author: kou (Kouhei Sutou) * Status: Open * Target version: 3.2 * ruby -v: ruby 3.2.2 (2023-03-30 revision e51014f9c0) [x64-mingw-ucrt] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I'm not sure whether this is an intentional behavior but it seems that `encoding: "utf-8"` doesn't change newline conversion but `encoding: "bom|utf-8"` changes newline conversion: ```ruby File.write("a.txt", "a\r\n") File.read("a.txt").bytes # => [97, 13, 10] File.open("a.txt", encoding: "utf-8") {|f| f.read.bytes} # => [97, 10, 10] File.open("a.txt", encoding: "bom|utf-8") {|f| f.read.bytes} # => [97, 10] XXX: \r\n -> \n File.open("a.txt", encoding: "bom|utf-8", universal_newline: false) {|f| f.read.bytes} # => [97, 13, 10] ``` Note that the `XXX: ` line the above codes. Is this an intentional behavior? -- https://bugs.ruby-lang.org/

3 2

[ruby-core:120183] [Ruby master Misc#20946] Proposing tomoya ishida (@tompng) as a Ruby committer
by matsuda (Akira Matsuda) 26 Dec '24

26 Dec '24

Issue #20946 has been reported by matsuda (Akira Matsuda). ---------------------------------------- Misc #20946: Proposing tomoya ishida (@tompng) as a Ruby committer https://bugs.ruby-lang.org/issues/20946 * Author: matsuda (Akira Matsuda) * Status: Open * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- I'd like to propose tomoya ishida (@tompng) as a Ruby committer. * As a maintainer of IRB / Reline since 2023, he has been continuously improving the REPL's stability and performance. Also, he authored type-based completion mechanism which is going to be included by default in the upcoming Ruby 3.4. * For some reasons, he is extraordinarily good at finding trivial and tricky syntax bugs. He already has reported massive numbers of very weird bugs to the new parsers. https://github.com/ruby/prism/issues/created_by/tompng I believe, keeping having such unique inputs from him would help improving the parsers and the language syntax in a way that only he can do. * He triggered and implemented Ruby 3.4's Hash#inspect improvement https://bugs.ruby-lang.org/issues/20433 https://github.com/ruby/ruby/pull/10924 * In fact ruby's repo already includes some more pieces of code written by him that show how talented programmer he is. (e.g. https://github.com/ruby/ruby/blob/master/sample/trick2022/01-tompng/entry.rb * He won this year's "Ruby Prize", which means he is considered an individual who made the most notable achievement for the community this year. https://rubyprize.jp/ -- https://bugs.ruby-lang.org/

7 9

[ruby-core:120189] [Ruby master Misc#20947] Propose ydah (Yudai Takada) as a Ruby committer
by yui-knk (Kaneko Yuichiro) 26 Dec '24

26 Dec '24

Issue #20947 has been reported by yui-knk (Kaneko Yuichiro). ---------------------------------------- Misc #20947: Propose ydah (Yudai Takada) as a Ruby committer https://bugs.ruby-lang.org/issues/20947 * Author: yui-knk (Kaneko Yuichiro) * Status: Open ---------------------------------------- I’d like to propose ydah (https://bugs.ruby-lang.org/users/52290) as a Ruby committer. He has contributed to parse.y. His contribution includes applying Lrama’s new feature to parse.y (https://github.com/ruby/ruby/pull/10050) fixing invalid syntax error (https://github.com/ruby/ruby/pull/11850) modification of ripper related codes (https://github.com/ruby/ruby/pull/10602) and so on. He fixes not only parse.y but also compile.c (https://github.com/ruby/ruby/pull/12275) He is passionate about making Ruby’s parser better. Then I want to make his contribution easy. I will be a mentor for him. -- https://bugs.ruby-lang.org/

4 6

[ruby-core:119881] [Ruby master Feature#20884] reserve "Ruby" toplevel module for Ruby language
by Dan0042 (Daniel DeLorme) 25 Dec '24

25 Dec '24

Issue #20884 has been reported by Dan0042 (Daniel DeLorme). ---------------------------------------- Feature #20884: reserve "Ruby" toplevel module for Ruby language https://bugs.ruby-lang.org/issues/20884 * Author: Dan0042 (Daniel DeLorme) * Status: Open ---------------------------------------- `Ruby` would be a convenient namespace for many features of the Ruby language, in particular APIs related to the interpreter. All these constants: RUBY_VERSION RUBY_RELEASE_DATE RUBY_PLATFORM RUBY_PATCHLEVEL RUBY_REVISION RUBY_COPYRIGHT RUBY_ENGINE RUBY_ENGINE_VERSION RUBY_DESCRIPTION would have made a lot of sense as `Ruby::Version` etc. `Thread::Backtrace::Location` would have made a lot of sense as `Ruby::Backtrace::Location` `RubyVM` is considered specific to CRuby; so `RubyVM::AbstractSyntaxTree` should be `Ruby::AbstractSyntaxTree` if it is meant to be present in other implementations. In #6648 there's a bit of contention over where `ruby_args` should be. `RubyVM`, `RbConfig`, `Process` have all been proposed, but `Ruby` would be an excellent choice. `Process.argv0` was added in Ruby 2.1 but the `Process` namespace is really about OS-level process control (fork, signals, euid, limits) while this argv0 is not (in `ps` it's neither value of COMMAND nor CMD) so it would have made sense as `Ruby.argv0` The "ruby" gem name is reserved, so there's no conflict. https://rubygems.org/gems/ruby All in all, "Ruby" is an appropriate namespace for many Ruby things. We don't want to break compatibility over this, but we could at least start small by reserving the namespace, and see how it grows from there. module Ruby Version = ::RUBY_VERSION end -- https://bugs.ruby-lang.org/

7 7