> as @Dan0042 (Daniel DeLorme) pointed out for example Just to clarify — maybe I missed something, but it seems there might be a slight misunderstanding. In his comment, Daniel mainly provided historical context about when `to_h` was ...ccmywish (Aoran Zeng)
1. `Kernel#Integer` uses `to_int` first and `to_i` second 2. `Kernel#Array` uses `to_ary` first and `to_a` second 3. `Kernel#Hash` only uses `to_hash` I don't quite understand why there is a need for differential treatment here. ...ccmywish (Aoran Zeng)
Recently the new version of `tracer` gem caught my eye. But I've noticed an anti-DRY pattern. I've noticed that many libs, CLI tools implement their own logic of color support on the terminal. These libs/CLI tools don't explicitly ...ccmywish (Aoran Zeng)
Ruby's default block comment is using `=begin` and `=end` ```ruby =begin Some block comments =end ``` However, we must place them at the top of the line, thus we can't indent them, for example: ```ruby class A class B c...ccmywish (Aoran Zeng)
HI @zverok, I think your proposition is a little different from what's reported here. ```ruby array = [:peanut, :butter, :and, :jelly] # 4 is out of range, but -> [] array[4,0] # 5 is out of range, but -> nil array[5,0] ```...ccmywish (Aoran Zeng)
kaiquekandykoga (Kaíque Koga) wrote in #note-1: > I think it can be interesting to open an issue at https://github.com/ruby/irb. Now here: https://github.com/ruby/irb/issues/361ccmywish (Aoran Zeng)
ccmywish (Aoran Zeng)11:49 AM Ruby Feature #21858: `Kernel#Hash` considers `to_h` too