@jeremyevans0 I see your point about how ivars take precedence over methods of the same name, but I think `it` is more like a block argument (well, a local variable) than a method, so I find this inconsistently really surprising: ```sh ...AMomchilov (Alexander Momchilov)
# Abstract Bare `rescue` keywords (either as a modifier like `foo rescue bar` or as clause of a `begin` block) should _not_ rescue `NameError` or `NoMethodError`. This behaviour is unexpected and hides bugs. ## Background Man...AMomchilov (Alexander Momchilov)
This is related to my `Hash#exchange_value` proposal, so I'll link that here. https://bugs.ruby-lang.org/issues/20300 I guess the difference is whether you already know the replacement you want to use instead, or if you'd like to comp...AMomchilov (Alexander Momchilov)
The `warn_cr_in_shebang()` function looks for `\r\n` together, but the `\r` should emit a warning, regardless if there's also a `\n` or not. ```ruby #!/usr/bin/ruby require "tempfile" require "open3" def run_rb(ruby_src) pu...AMomchilov (Alexander Momchilov)
vo.x (Vit Ondruch) wrote in #note-13: > This does not help testing with Ruby 3.3.2 Hmmm that's a bit surprising. Thanks for taking the time to try that. Ok, let's go a bit more conservative, could you please test again with my [...AMomchilov (Alexander Momchilov)
mame (Yusuke Endoh) wrote in #note-24: > It was originally intended as a method to improve the efficiency of `Set#add?`, but the use case was shifted to a method for thread safety. This history makes the use case less persuasive. T...AMomchilov (Alexander Momchilov)
nobu (Nobuyoshi Nakada) wrote in #note-17: > I want `ENV.exchange_value` rather than `Hash#exchange_value`. Is there a reason to put it on `ENV`, but *not* on `Hash`? That seems like a needless restriction to me.AMomchilov (Alexander Momchilov)
shyouhei (Shyouhei Urabe) wrote in #note-8: > Why not: Because I didn't think of that :) I would be okay with it, but I think the thread safety issue is also worth solving. The implementation I'm proposing solves both the performa...AMomchilov (Alexander Momchilov)
@matheusrich Thanks for putting together that list! In general, I like the idea of having this method support an optional block, but we would need to benchmark it to ensure it doesn't have an undesired slow down in the `exchange_value(:...AMomchilov (Alexander Momchilov)
AMomchilov (Alexander Momchilov)06:43 PM Ruby Bug #21139: Prism and parse.y parses `it = it` differently