I think it's an off-by-one bug. [This +1 seems](https://github.com/ruby/ruby/pull/16951) to fix it, though admittedly this code path is pretty complicated and I'm not sure of the exact memory layout. AMomchilov (Alexander Momchilov)
Reading the `label` of a `Thread::Backtrace::Location` (directly or indirectly via e.g. `to_s`) segfauls if called from within `Thread.each_caller_location(1, 1) { it.label }`. Reading the `lineno` or `path` seems to not cause any pro...AMomchilov (Alexander Momchilov)
Did you think you could fly under the radar with that semi-colon? That's not acceptable corner to cut. For proper POSIX shell compatibility, it's imperative that the Ruby grammar be extended to accept `:` as a bare keyword, equivalent ...AMomchilov (Alexander Momchilov)
@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)
AMomchilov (Alexander Momchilov)09:19 PM Ruby Bug #22070: `Thread.each_caller_location(1, 1)` segfaults when called from a cfunc