Conversation
|
@kares Nice work and specs here! |
|
@eregon thx, I thought the work-flow is that you pick those eventually back to ruby/rubyspec. |
…e returned not obj
|
@kares For new feature specs I think it's more beneficial to PR against the ruby/rubyspec repo. A guard of minimal version 2.3 will be needed anyway for this spec to pass on older versions, so this spec will only run when JRuby declares RUBY_VERSION to be "2.3.x" (it's possible to ignore such a guard with --unguarded while developing). Yes, please remove them from here if you do the PR so there is no chance for conflict :) |
There was a problem hiding this comment.
Missing a terminating newline character here.
|
put the commits into ruby-2.3 which should merge to master after 2.3 final when 9.1.0 is released |
[].dig(0)and{}.dig(:a)as introduced by MRI 2.3.0.preview1