Herwin

```ruby a = [1, 2, 3] p a.replace(a) p a ``` Arrays have the same issue. ```ruby s = 'hello, world' p s.replace(s) p s ```` But Strings doe not...

https://github.com/natalie-lang/natalie/blob/master/lib/natalie/compiler/pass1.rb#L2361-L2380 We do something similar with regexp: parse it at compile time, and generate instructions to raise an exception if it cannot be parsed (#2058). It's one of those things...

```c++ Value ExceptionObject::match_rescue_array(Env *env, Value ary) { // NOTE: Even though LocalJumpError is a StandardError, we only // want it to match if it was explicitly given in the array,...

Tried that, first my music started to stutter, then my machine became completely unresponsive and I had to force a reboot. My gut feeling tells me just stripping away that...

```ruby def build_and_call_proc # FIXME: need to wrap call site not just block Proc.new { return 42 }.call raise 'Never reached, return in proc returns at the method scope' end...

I was just thinking about this again: do the move semantics still make sense? They made sense when `Args` still contained their own array with arguments that got copied over...

It looks like it breaks on `%04Y` in `strftime`, which might be a GNU extension (thus not available in MacOS). It's probably easier to start working on `Time#strftime`, this needs...

The retry idea would change the requirements a bit. We might depend on the before/after hooks for setup/teardown, So this means we have two options. Option 1: wrap the `it`...

Perhaps as a slight change to Richard's proposed syntax: ```ruby it "reads data from the connection", NATFIXME: { status: :unreliable, exception: Errno::EAGAIN, message: 'Resource temporarily unavailable' } do # or...

I guess the intention of this change has shifted a bit when I was working on it. Since the internal interface of our specs runner is incompatible with the upstream...