Add Fiber# and Fiber#= and restore Thread# and Thread#= to their original behavior
Ruby 3 API cleanup suggestion.
The Thread and Fiber classes have a very odd API for setting/getting thread local and fiber local variables. With Ruby 3 coming soon, this is a perfect opportunity to make this API more coherent and return to the Principal of Least Surprise. The concept of Fibers and Threads should be completely separated and we should no longer assume that a Fiber is attached to any particular Thread.
I suggest this:
class Fiber # Gets a fiber-local variable. def (index) ... end # Sets a fiber-local variable. def =(index, value) ... end # Returns true if the given +key+ exists as a fiber-local variable. def key?(key) ... end # Returns an array of fiber-local variable names as symbols. def keys ... end end class Thread # Gets a thread-local variable. def (index) ... end # Sets a thread-local variable. def =(index, value) ... end # Returns true if the given +key+ exists as a thread-local variable. def key?(key) ... end # Returns an array of thread-local variable names as symbols. def keys ... end end
Thread#thread_variables since that behavior is already covered by
Thread#=. The APIs for both Thread and Fiber are more coherent and less surprising with these changes.
#2 [ruby-core:82766] Updated by Eregon (Benoit Daloze) 11 days ago
Another idea which is related to #13245 would be to have these as class methods on Fiber and Thread (Thread[:foo]; Thread[:foo] = :bar; Thread.keys; Thread.key? :foo),
which would limit only accessing variables of the current fiber/thread.
It would allow to keep old methods for compatibility and maybe progressively deprecate them.
#3 [ruby-core:82789] Updated by shevegen (Robert A. Heiler) 9 days ago
I have nothing against the suggestion itself. However, there is no general, universal "Principal of Least Surprise".
To the topic, Threads and Fibers - I have used Threads sometimes but rarely. I haven't yet used Fibers. Without knowing any particular use case, I have a hard time trying to want to use something new.
For me, well aside from the suggestion here, I find this all way too complicated. Threads were actually quite simple... no idea how Fibers fit into anything there... or Mutex. I hope someone will simplify this all, no matter how. :)
As for ruby 3.0, I do not think it is "coming soon". Ruby 2.5 will come this year, I am not sure that ruby 3.0 will already be the very next ... matz said in one presentation that there is "tons of work" still about to happen for ruby 3, so I don't think that is all going to happen over night (if all the mentioned features that matz spoke about will go into Ruby 3.x, and I guess the core team wants the first ruby 3 release to be stable rather than unstable, which also will take a bit).
#4 [ruby-core:82794] Updated by cremes (Chuck Remes) 9 days ago
Ideally some of these changes could be rolled out in 2.x versions with deprecation notices for those methods whose behavior will change or those methods will be eliminated. For the 3.0 release, the deprecated methods should be removed entirely. Yes, these are breaking changes. Ruby3 is a wonderful opportunity to make the core APIs more consistent. If we miss this chance, it will be years (a decade?) before we get another chance to fix these inconsistencies.