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

[ruby-core:116864] [Ruby master Bug#20283] Build failed since Ruby 3.2.3 if Xcode.app was renamed to space contained name.
by watson1978 (Shizuo Fujita) 20 Feb '24

20 Feb '24

Issue #20283 has been reported by watson1978 (Shizuo Fujita). ---------------------------------------- Bug #20283: Build failed since Ruby 3.2.3 if Xcode.app was renamed to space contained name. https://bugs.ruby-lang.org/issues/20283 * Author: watson1978 (Shizuo Fujita) * Status: Open * Priority: Normal * Backport: 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- When I renamed Xcode.app to space contained name (like `Xcode 15.2.0.app`), then I met build error with Ruby 3.2.3 and Ruby 3.3.0. (Ruby 3.2.2 can be built with successfully.) ## How to reproduce ``` $ sudo mv /Applications/Xcode.app '/Applications/Xcode 15.2.app' $ sudo xcode-select --switch '/Applications/Xcode 15.2.app' $ tar xzf ruby-3.2.3.tar.xz $ cd ruby-3.2.3 $ ./configure $ make V=1 : clang -fdeclspec -O3 -fno-fast-math -ggdb3 -Wall -Wextra -Wextra-tokens -Wdeprecated-declarations -Wdivision-by-zero -Wdiv-by-zero -Wimplicit-function-declaration -Wimplicit-int -Wmisleading-indentation -Wpointer-arith -Wshorten-64-to-32 -Wwrite-strings -Wold-style-definition -Wmissing-noreturn -Wno-cast-function-type -Wno-constant-logical-operand -Wno-long-long -Wno-missing-field-initializers -Wno-overlength-strings -Wno-parentheses-equality -Wno-self-assign -Wno-tautological-compare -Wno-unused-parameter -Wno-unused-value -Wunused-variable -Wundef -pipe -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -fstack-protector-strong -fno-strict-overflow -fvisibility=hidden -DRUBY_EXPORT -fPIE -I. -I.ext/include/arm64-darwin23 -I./include -I. -I./enc/unicode/15.0.0 -I/opt/homebrew/include -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE -D_DARWIN_UNLIMITED_SELECT -D_REENTRANT -o dmyenc.o -c dmyenc.c rustc --crate-name=yjit --crate-type=staticlib --edition=2021 -g -C opt-level=3 -C overflow-checks=on '--out-dir=/Users/watson/prj/ruby-3.2.3/yjit/target/release/' ./yjit/src/lib.rs touch yjit/target/release/libyjit.a clang -fdeclspec -O3 -fno-fast-math -ggdb3 -Wall -Wextra -Wextra-tokens -Wdeprecated-declarations -Wdivision-by-zero -Wdiv-by-zero -Wimplicit-function-declaration -Wimplicit-int -Wmisleading-indentation -Wpointer-arith -Wshorten-64-to-32 -Wwrite-strings -Wold-style-definition -Wmissing-noreturn -Wno-cast-function-type -Wno-constant-logical-operand -Wno-long-long -Wno-missing-field-initializers -Wno-overlength-strings -Wno-parentheses-equality -Wno-self-assign -Wno-tautological-compare -Wno-unused-parameter -Wno-unused-value -Wunused-variable -Wundef -pipe -L. -L/opt/homebrew/lib -fstack-protector-strong -fstack-protector-strong -Wl,-pie -framework CoreFoundation main.o dmydln.o miniinit.o dmyext.o array.o ast.o bignum.o class.o compar.o compile.o complex.o cont.o debug.o debug_counter.o dir.o dln_find.o encoding.o enum.o enumerator.o error.o eval.o file.o gc.o hash.o inits.o io.o io_buffer.o iseq.o load.o marshal.o math.o memory_view.o mjit.o mjit_c.o node.o numeric.o object.o pack.o parse.o proc.o process.o ractor.o random.o range.o rational.o re.o regcomp.o regenc.o regerror.o regexec.o regparse.o regsyntax.o ruby.o scheduler.o shape.o signal.o sprintf.o st.o strftime.o string.o struct.o symbol.o thread.o time.o transcode.o transient_heap.o util.o variable.o version.o vm.o vm_backtrace.o vm_dump.o vm_sync.o vm_trace.o yjit.o coroutine/arm64/Context.o enc/ascii.o enc/us_ascii.o enc/unicode.o enc/utf_8.o enc/trans/newline.o explicit_bzero.o setproctitle.o addr2line.o yjit/target/release/libyjit.a -lgmp -ldl -lobjc -lpthread -lpthread -o miniruby ld: warning: ignoring duplicate libraries: '-lpthread' ld: Undefined symbols: _coroutine_transfer, referenced from: _fiber_setcontext in cont.o clang: error: linker command failed with exit code 1 (use -v to see invocation) ``` ## Environment - Apple M1 Max - macOS 14.3.1 - clang 15.0.0 (clang-1500.1.0.2.5) - rustc 1.75.0 ## Note This problem occurs on Intel Mac and Apple M1 Mac both. -- https://bugs.ruby-lang.org/

2 1

[ruby-core:116670] [Ruby master Feature#20257] Rearchitect Ripper
by yui-knk (Kaneko Yuichiro) 20 Feb '24

20 Feb '24

Issue #20257 has been reported by yui-knk (Kaneko Yuichiro). ---------------------------------------- Feature #20257: Rearchitect Ripper https://bugs.ruby-lang.org/issues/20257 * Author: yui-knk (Kaneko Yuichiro) * Status: Open * Priority: Normal ---------------------------------------- # Abstract Rearchitect Ripper to provide whole semantic analysis support for Ripper and improve maintainability of Ripper. This rearchitecture is achieved by modifying Lrama parser generator. # Background and problem Ripper is used for parsing ruby code, for example irb and rdoc use Ripper for parsing source codes. Ripper and Ruby parser share the algorithm of parsing, however internal logic of Ripper is different from parser. The differences cause three problems: 1. Ripper can not execute some semantic analysis. https://bugs.ruby-lang.org/issues/10436 is an example of this limitaion. `m(&nil) {}` raises syntax error but `Ripper.sexp("m(&nil) {}")` doesn't. 2. Ripper can not recognize regexp named capture. https://bugs.ruby-lang.org/issues/18988 is an example. 3. Makes prase.y complex. For example, the implementation of `new_array_pattern` is completely different between [parser](https://github.com/ruby/ruby/blob/1949a04f81311660e2d0ec002c48115c6… and [ripper](https://github.com/ruby/ruby/blob/1949a04f81311660e2d0ec002c48115c6…. These problems come from the fact parser and Ripper use semantic value stack differently. Parser stores Node on the stack in many rules but Ripper stores Ruby Object returned by callback method. Therefore Ripper can not execute semantic analysis which requires Node (#1). Values on the stack are different then they need to implement same name functions differently (#3). This leads different behavior like #2 because they have different `match_op` function. # Proposal Introduce new semantic value stack for Ripper so that Ripper can manage both Node and Ruby Object separately. Lrama will provide some callback entry points and new special variable for actions. Lrama will support these callback directives, specified function is called when the event happens * %after-shift function_name * %before-reduce function_name * %after-reduce function_name * %after-shift-error-token function_name * %after-pop-stack function_name Lrama also provides `$:n` variable to access index of each grammar symbols. The variable is translated to the minus index from the top of the stack. For example ```c primary: k_if expr_value then compstmt if_tail k_end { /*% ripper: if!($:2, $:4, $:5) %*/ /* $:2 = -5, $:4 = -3, $:5 = -2. */ } ``` We can implement separated stack for Ruby Object by these features. # Implementation note ## New fields of struct parser_params * `VALUE s_value`: Holds Ruby Object returned by Ripper callback method call. * `VALUE s_lvalue`: Holds Ruby Object responding to LHS of the rule. * `VALUE s_value_stack`: Stack for Ruby Object. It's actually ruby array. These fields are added only when it's Ripper. ## The role of callback functions * %after-shift: Push `s_value` to `s_value_stack`. * %before-reduce: Assign the first Ruby Object of RHS to `s_lvalue` (similar with `$$ = $1`). * %after-reduce: Pop `s_value_stack` `rhs.len` times then push `s_lvalue` to `s_value_stack`. * %after-shift-error-token: Push `nil` to `s_value_stack`. This `nil` stands for `error` token. * %after-pop-stack: Pop `s_value_stack` `len` times. This is needed to emulate panic mode. # Achievement These bugs are fixed. * [Bug 10436](https://bugs.ruby-lang.org/issues/10436) "ruby -c and ripper inconsistency: m(&nil) {}" * [Bug 18988](https://bugs.ruby-lang.org/issues/18988) "Ripper cannot parse some code that has regexp named capture" * [Bug 20055](https://bugs.ruby-lang.org/issues/20055) "Ripper seems to skip some checks like `void value expression` and `duplicated variable name`" This means [all of Ripper open bugs tickets](https://bugs.ruby-lang.org/projects/ruby-master/issues?utf8=%E2%9C… which are related current architecture will be closed. # Links * Lrama Implementaion: https://github.com/ruby/lrama/pull/367 * Ruby Implementaion: TBD -- https://bugs.ruby-lang.org/

3 3

[ruby-core:116857] [Ruby master Feature#18576] Rename `ASCII-8BIT` encoding to `BINARY`
by duerst 19 Feb '24

19 Feb '24

Issue #18576 has been updated by duerst (Martin Dürst). What about ``` >> "fée" + "fée".b (irb):8:in `+': incompatible character encodings: UTF-8 and BINARY (ASCII-8BIT) (Encoding::CompatibilityError) ``` This still leaves "ASCII-8BIT" in (because I think it's important to help people understand that BINARY and ASCII-8BIT are the same). [It also keeps the wart of consecutive parentheticals, but that can be dealt with separately.] ---------------------------------------- Feature #18576: Rename `ASCII-8BIT` encoding to `BINARY` https://bugs.ruby-lang.org/issues/18576#change-106889 * Author: byroot (Jean Boussier) * Status: Open * Priority: Normal * Target version: 3.4 ---------------------------------------- ### Context I'm now used to it, but something that confused me for years was errors such as: ```ruby >> "fée" + "\xFF".b (irb):3:in `+': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError) ``` When you aren't that familiar with Ruby, it's really not evident that `ASCII-8BIT` basically means "no encoding" or "binary". And even when you know it, if you don't read carefully it's very easily confused with `US-ASCII`. The `Encoding::BINARY` alias is much more telling IMHO. ### Proposal Since `Encoding::ASCII_8BIT` has been aliased as `Encoding::BINARY` for years, I think renaming it to `BINARY` and then making asking `ASCII_8BIT` the alias would significantly improve usability without backward compatibility concerns. The only concern I could see would be the consistency with a handful of C API functions: - `rb_encoding *rb_ascii8bit_encoding(void)` - `int rb_ascii8bit_encindex(void)` - `VALUE rb_io_ascii8bit_binmode(VALUE io)` But that's for much more advanced users, so I don't think it's much of a concern. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116856] [Ruby master Feature#13557] there's no way to pass backtrace locations as a massaged backtrace
by Dan0042 (Daniel DeLorme) 19 Feb '24

19 Feb '24

Issue #13557 has been updated by Dan0042 (Daniel DeLorme). byroot (Jean Boussier) wrote in #note-7: > Which I think is simple enough to not warrant and extra `skip:` parameter to `raise`. Good point, I'm convinced. ---------------------------------------- Feature #13557: there's no way to pass backtrace locations as a massaged backtrace https://bugs.ruby-lang.org/issues/13557#change-106888 * Author: sylvain.joyeux (Sylvain Joyeux) * Status: Open * Priority: Normal ---------------------------------------- When re-raising exceptions, it is sometimes useful to "massage" the backtrace (especially in DSLs). There is currently no way to do it using only backtrace locations. This causes the new exception to have #backtrace_locations return nil, and thus makes backtrace_locations unreliable as a whole. Example: ~~~ def test raise ArgumentError, "", caller_locations end begin test rescue ArgumentError => e p e.backtrace_locations end ~~~ attempting to pass `caller_location` to `Kernel#raise` in the `test` method fails with `bla.rb:2:in `set_backtrace': backtrace must be Array of String (TypeError)` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116855] [Ruby master Feature#18576] Rename `ASCII-8BIT` encoding to `BINARY`
by Dan0042 (Daniel DeLorme) 19 Feb '24

19 Feb '24

Issue #18576 has been updated by Dan0042 (Daniel DeLorme). I've come to realize something; when an ASCII-8BIT string contains only ascii characters, it behaves exactly like a US-ASCII string and in such a case it feels unnatural to call it "binary" (at least for me). But as soon as there is a non-ascii byte, it becomes incompatible with every other encoding and then truly deserves to be called BINARY. And that's when encoding errors occur. So in error messages, "BINARY" makes perfect sense to me since the error occurs due to the string being in "binary" state rather than "ascii-only" state. The distinction may be irrelevant to others but at least it has helped me put into words and understand why it felt so uncomfortable to change the name to "BINARY". Just my 2¢ ---------------------------------------- Feature #18576: Rename `ASCII-8BIT` encoding to `BINARY` https://bugs.ruby-lang.org/issues/18576#change-106887 * Author: byroot (Jean Boussier) * Status: Open * Priority: Normal * Target version: 3.4 ---------------------------------------- ### Context I'm now used to it, but something that confused me for years was errors such as: ```ruby >> "fée" + "\xFF".b (irb):3:in `+': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError) ``` When you aren't that familiar with Ruby, it's really not evident that `ASCII-8BIT` basically means "no encoding" or "binary". And even when you know it, if you don't read carefully it's very easily confused with `US-ASCII`. The `Encoding::BINARY` alias is much more telling IMHO. ### Proposal Since `Encoding::ASCII_8BIT` has been aliased as `Encoding::BINARY` for years, I think renaming it to `BINARY` and then making asking `ASCII_8BIT` the alias would significantly improve usability without backward compatibility concerns. The only concern I could see would be the consistency with a handful of C API functions: - `rb_encoding *rb_ascii8bit_encoding(void)` - `int rb_ascii8bit_encindex(void)` - `VALUE rb_io_ascii8bit_binmode(VALUE io)` But that's for much more advanced users, so I don't think it's much of a concern. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116848] [Ruby master Feature#11446] Possible work around for the requirement to supplying arguments like this: .map(&:method, <arguments>)
by artemb (Artem Borodkin) 19 Feb '24

19 Feb '24

Issue #11446 has been updated by artemb (Artem Borodkin). Are there any proposal issues regarding the addition of argument and block support for the ```.each(&:method, args) do; end``` syntax? It seems quite feasible to support it natively. ``` ruby module Enumerable def each_call(method, *args, &) = each { _1.send method, *args, & } def map_call!(method, *args, &) = map! { _1.send method, *args, & } # ... end # [1,2].map! &:+, 1 [1,2].map_call! :+, 1 # [].each &:instance_eval do %w[1 2].each_call :instance_eval do @v = 1 end ``` ---------------------------------------- Feature #11446: Possible work around for the requirement to supplying arguments like this: .map(&:method, <arguments>) https://bugs.ruby-lang.org/issues/11446#change-106877 * Author: jikkujose (Jikku Jose) * Status: Open * Priority: Normal ---------------------------------------- Any chance this [work around](http://stackoverflow.com/questions/23695653/can-you-supply-argument… can be considered to be part of the language. Seems to be a pretty neat. NB: Matz seems to be interested in having this added: Check his [tweet](https://twitter.com/yukihiro_matz/status/632016695016620033). -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116845] [Ruby master Feature#18576] Rename `ASCII-8BIT` encoding to `BINARY`
by byroot (Jean Boussier) 19 Feb '24

19 Feb '24

Issue #18576 has been updated by byroot (Jean Boussier). Proposed patch: https://github.com/ruby/ruby/pull/10018 I used my initial suggestion: `ASCII-8BIT (BINARY)`, but if the parentheses are deemed to much, I'm happy to adjust. ---------------------------------------- Feature #18576: Rename `ASCII-8BIT` encoding to `BINARY` https://bugs.ruby-lang.org/issues/18576#change-106871 * Author: byroot (Jean Boussier) * Status: Open * Priority: Normal * Target version: 3.4 ---------------------------------------- ### Context I'm now used to it, but something that confused me for years was errors such as: ```ruby >> "fée" + "\xFF".b (irb):3:in `+': incompatible character encodings: UTF-8 and ASCII-8BIT (Encoding::CompatibilityError) ``` When you aren't that familiar with Ruby, it's really not evident that `ASCII-8BIT` basically means "no encoding" or "binary". And even when you know it, if you don't read carefully it's very easily confused with `US-ASCII`. The `Encoding::BINARY` alias is much more telling IMHO. ### Proposal Since `Encoding::ASCII_8BIT` has been aliased as `Encoding::BINARY` for years, I think renaming it to `BINARY` and then making asking `ASCII_8BIT` the alias would significantly improve usability without backward compatibility concerns. The only concern I could see would be the consistency with a handful of C API functions: - `rb_encoding *rb_ascii8bit_encoding(void)` - `int rb_ascii8bit_encindex(void)` - `VALUE rb_io_ascii8bit_binmode(VALUE io)` But that's for much more advanced users, so I don't think it's much of a concern. -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116844] [Ruby master Feature#13557] there's no way to pass backtrace locations as a massaged backtrace
by byroot (Jean Boussier) 19 Feb '24

19 Feb '24

Issue #13557 has been updated by byroot (Jean Boussier). > So it would be nice to have a shortcut idiom for this, like perhaps raise Error, "message", skip: 3 With my patch it would be: ```ruby raise Error, "message", caller_locations(3) ``` Which I think is simple enough to not warrant and extra `skip:` parameter to `raise`. ---------------------------------------- Feature #13557: there's no way to pass backtrace locations as a massaged backtrace https://bugs.ruby-lang.org/issues/13557#change-106870 * Author: sylvain.joyeux (Sylvain Joyeux) * Status: Open * Priority: Normal ---------------------------------------- When re-raising exceptions, it is sometimes useful to "massage" the backtrace (especially in DSLs). There is currently no way to do it using only backtrace locations. This causes the new exception to have #backtrace_locations return nil, and thus makes backtrace_locations unreliable as a whole. Example: ~~~ def test raise ArgumentError, "", caller_locations end begin test rescue ArgumentError => e p e.backtrace_locations end ~~~ attempting to pass `caller_location` to `Kernel#raise` in the `test` method fails with `bla.rb:2:in `set_backtrace': backtrace must be Array of String (TypeError)` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116843] [Ruby master Feature#13557] there's no way to pass backtrace locations as a massaged backtrace
by byroot (Jean Boussier) 19 Feb '24

19 Feb '24

Issue #13557 has been updated by byroot (Jean Boussier). Proposed patch here if someone feels like reviewing it: https://github.com/ruby/ruby/pull/10017 ---------------------------------------- Feature #13557: there's no way to pass backtrace locations as a massaged backtrace https://bugs.ruby-lang.org/issues/13557#change-106869 * Author: sylvain.joyeux (Sylvain Joyeux) * Status: Open * Priority: Normal ---------------------------------------- When re-raising exceptions, it is sometimes useful to "massage" the backtrace (especially in DSLs). There is currently no way to do it using only backtrace locations. This causes the new exception to have #backtrace_locations return nil, and thus makes backtrace_locations unreliable as a whole. Example: ~~~ def test raise ArgumentError, "", caller_locations end begin test rescue ArgumentError => e p e.backtrace_locations end ~~~ attempting to pass `caller_location` to `Kernel#raise` in the `test` method fails with `bla.rb:2:in `set_backtrace': backtrace must be Array of String (TypeError)` -- https://bugs.ruby-lang.org/

1 0

[ruby-core:116837] [Ruby master Misc#20279] `respond_to_missing?` in BasicObject documentation correct?
by ioquatix (Samuel Williams) 19 Feb '24

19 Feb '24

Issue #20279 has been reported by ioquatix (Samuel Williams). ---------------------------------------- Misc #20279: `respond_to_missing?` in BasicObject documentation correct? https://bugs.ruby-lang.org/issues/20279 * Author: ioquatix (Samuel Williams) * Status: Open * Priority: Normal ---------------------------------------- Considering the documentation here: https://ruby-doc.org/3.2.2/BasicObject.html Introduced in: https://github.com/ruby/ruby/commit/3eb7d2b33e3f8555d81db5369eb6fb7100a91e63 I wondered if `or super` is correct in `respond_to_missing?`. For example: ``` irb(main):001* class MyObjectSystem < BasicObject irb(main):002* DELEGATE = [:puts, :p] irb(main):003* irb(main):004* def method_missing(name, *args, &block) irb(main):005* return super unless DELEGATE.include? name irb(main):006* ::Kernel.send(name, *args, &block) irb(main):007* end irb(main):008* irb(main):009* public def respond_to_missing?(name, include_private = false) irb(main):010* DELEGATE.include?(name) or super irb(main):011* end irb(main):012> end => :respond_to_missing? irb(main):013> MyObjectSystem.new.respond_to_missing?(:foo) (irb):5:in `method_missing': super: no superclass method `respond_to_missing?' for an instance of MyObjectSystem (NoMethodError) from (irb):10:in `respond_to_missing?' from (irb):13:in `<main>' from <internal:kernel>:187:in `loop' from /home/samuel/.gem/ruby/3.3.0/gems/irb-1.11.2/exe/irb:9:in `<top (required)>' from /home/samuel/.gem/ruby/3.3.0/bin/irb:25:in `load' from /home/samuel/.gem/ruby/3.3.0/bin/irb:25:in `<main>' ``` It looks wrong to me. In addition, I'd like to know in what situations `BasicObject` should define `respond_to_missing?` - because I was under the impression it was called by `method_missing`. Does `BasicObject#method_missing` have this behaviour? Maybe we can improve the documentation cc @burdettelamar -- https://bugs.ruby-lang.org/

2 4