From: "nobu (Nobuyoshi Nakada) via ruby-core" <ruby-core@...>
Date: 2024-12-23T11:01:29+00:00
Subject: [ruby-core:120377] [Ruby master Bug#20978] Ractor[]/Thread[]/Fiber[] behavior difference

Issue #20978 has been updated by nobu (Nobuyoshi Nakada).


Before commit:d4c720a91bc7bb9ff31810e1720acffb939f7a2f, fiber storage used `rb_check_id` to check arguments.
This function tries to convert a non-Symbol value to a String.
So this bug is a regression, I think.

----------------------------------------
Bug #20978: Ractor[]/Thread[]/Fiber[] behavior difference
https://bugs.ruby-lang.org/issues/20978#change-111154

* Author: zverok (Victor Shepelev)
* Status: Open
* ruby -v: ruby 3.4.0dev (2024-12-22T06:08:19Z master 3808d29e20) +PRISM [x86_64-linux]
* Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN
----------------------------------------
`Ractor.[]` and `.[]=` support string and symbol keys (treating them by string value, and also accepting anything responding to `#to_str`):

```ruby
Ractor[:value] = 10
Ractor[:value] #=> 10
Ractor['value'] #=> 10
o = Object.new
def o.to_str = 'value'
Ractor[o] #=> 10

Ractor[1]
# in 'Ractor.[]': 1 is not a symbol nor a string (TypeError)
```

But `Fiber.[]` only accept symbols:
```ruby
Fiber[:value] = 10
Fiber['value']
# in 'Fiber.[]': wrong argument type String (expected Symbol) (TypeError)
```

`Thread#[]` and `#[]=` behave like Ractor���s. 

(The documentation for Fiber and Thread follows the reality���while Ractor���s current docs don���t specify key type at all���but the discrepancy feels somewhat weird.)



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/