Age | Commit message (Collapse) | Author |
|
since 5512353d97250e85c13bf10b9b32e750478cf474
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4414
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4412
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4413
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4411
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4410
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4406
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4407
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4408
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4409
|
|
This reverts commit a224ce8150f2bc687cf79eb415c931d87a4cd247.
Turns out the checks are needed to handle splatting an array with an
empty ruby2 keywords hash.
Notes:
Merged-By: XrXr
|
|
In Ruby 2.7, empty keyword splats could be added back for backwards
compatibility. However, that stopped in Ruby 3.0.
|
|
These two checks are surrounded by an if that ensures the
call site is not a kw splat call site.
Notes:
Merged: https://github.com/ruby/ruby/pull/4404
Merged-By: XrXr
|
|
If a class has been refined but does not have an origin class,
there is a single method entry marked with VM_METHOD_TYPE_REFINED,
but it contains the original method entry. If the original method
entry is present, we shouldn't skip the method when searching even
when skipping refined methods.
Fixes [Bug #17519]
Notes:
Merged: https://github.com/ruby/ruby/pull/4357
|
|
|
|
It doesn't return `nil` but raises an exception, as explained a few lines after
Notes:
Merged: https://github.com/ruby/ruby/pull/4403
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/4402
|
|
|
|
|
|
|
|
`#=~` builds `MatchData`, requiring extra allocations as compared to
`#match?`, which returns a boolean w/o having to build the `MatchData`.
https://github.com/ruby/uri/commit/158f58a9cc
|
|
https://github.com/ruby/uri/commit/0f0057e1b2
|
|
Tests pass on Ruby 2.4, but not on Ruby 2.3.
https://github.com/ruby/uri/commit/594418079a
|
|
This allows tests to pass on Ruby 2.4-2.6.
Fixes #19
https://github.com/ruby/uri/commit/67ca99ca87
|
|
https://github.com/ruby/uri/commit/d47dae2f8e
|
|
https://github.com/ruby/uri/commit/3b7ccfd835
|
|
These Java properties, retrieved from JRuby's "Java env" ENV_JAVA,
allow JRuby users to use the same proxy properties the rest of the
Java platform uses.
This resolves https://bugs.ruby-lang.org/issues/11194
https://github.com/ruby/uri/commit/3bd2bcc95a
|
|
https://github.com/ruby/net-imap/commit/31f96ea884
|
|
Fixes #14
https://github.com/ruby/net-imap/commit/39d39ff9bb
|
|
|
|
|
|
Having the separate dir makes testing difficult and doesn't
reflect the structure the gem will eventually have. We can filter
these files out if necessary when building the CRuby gem.
https://github.com/ruby/io-console/commit/881010447c
|
|
https://github.com/ruby/io-console/commit/c17b8cf3a9
|
|
|
|
This gem exposes no executables.
https://github.com/ruby/benchmark/commit/ff1ef7ae06
|
|
method name.
https://github.com/ruby/benchmark/commit/02ce298d3e
|
|
The gem exposes no executables
https://github.com/ruby/cgi/commit/cd7106ad97
|
|
ruby version
Also, remove pointless assert_nothing_raised(ArgumentError) while
here.
https://github.com/ruby/cgi/commit/c05edf5608
|
|
https://github.com/ruby/cgi/commit/2b1c2e21a4
|
|
https://github.com/ruby/time/commit/c784e4f166
|
|
add_ensure_iseq() adds ensure block to the end of
jump such as next/redo/return. However, if the rescue
cause are in the body, this rescue catches the exception
in ensure clause.
iter do
next
rescue
R
ensure
raise
end
In this case, R should not be executed, but executed without this patch.
Fixes [Bug #13930]
Fixes [Bug #16618]
A part of tests are written by @jeremyevans https://github.com/ruby/ruby/pull/4291
Notes:
Merged: https://github.com/ruby/ruby/pull/4399
|
|
This was previously only used by the multiple assignment code, but
is no longer needed after the multiple assignment execution order
fix.
Notes:
Merged: https://github.com/ruby/ruby/pull/4398
|
|
|
|
In regular assignment, Ruby evaluates the left hand side before
the right hand side. For example:
```ruby
foo[0] = bar
```
Calls `foo`, then `bar`, then `[]=` on the result of `foo`.
Previously, multiple assignment didn't work this way. If you did:
```ruby
abc.def, foo[0] = bar, baz
```
Ruby would previously call `bar`, then `baz`, then `abc`, then
`def=` on the result of `abc`, then `foo`, then `[]=` on the
result of `foo`.
This change makes multiple assignment similar to single assignment,
changing the evaluation order of the above multiple assignment code
to calling `abc`, then `foo`, then `bar`, then `baz`, then `def=` on
the result of `abc`, then `[]=` on the result of `foo`.
Implementing this is challenging with the stack-based virtual machine.
We need to keep track of all of the left hand side attribute setter
receivers and setter arguments, and then keep track of the stack level
while handling the assignment processing, so we can issue the
appropriate topn instructions to get the receiver. Here's an example
of how the multiple assignment is executed, showing the stack and
instructions:
```
self # putself
abc # send
abc, self # putself
abc, foo # send
abc, foo, 0 # putobject 0
abc, foo, 0, [bar, baz] # evaluate RHS
abc, foo, 0, [bar, baz], baz, bar # expandarray
abc, foo, 0, [bar, baz], baz, bar, abc # topn 5
abc, foo, 0, [bar, baz], baz, abc, bar # swap
abc, foo, 0, [bar, baz], baz, def= # send
abc, foo, 0, [bar, baz], baz # pop
abc, foo, 0, [bar, baz], baz, foo # topn 3
abc, foo, 0, [bar, baz], baz, foo, 0 # topn 3
abc, foo, 0, [bar, baz], baz, foo, 0, baz # topn 2
abc, foo, 0, [bar, baz], baz, []= # send
abc, foo, 0, [bar, baz], baz # pop
abc, foo, 0, [bar, baz] # pop
[bar, baz], foo, 0, [bar, baz] # setn 3
[bar, baz], foo, 0 # pop
[bar, baz], foo # pop
[bar, baz] # pop
```
As multiple assignment must deal with splats, post args, and any level
of nesting, it gets quite a bit more complex than this in non-trivial
cases. To handle this, struct masgn_state is added to keep
track of the overall state of the mass assignment, which stores a linked
list of struct masgn_attrasgn, one for each assigned attribute.
This adds a new optimization that replaces a topn 1/pop instruction
combination with a single swap instruction for multiple assignment
to non-aref attributes.
This new approach isn't compatible with one of the optimizations
previously used, in the case where the multiple assignment return value
was not needed, there was no lhs splat, and one of the left hand side
used an attribute setter. This removes that optimization. Removing
the optimization allowed for removing the POP_ELEMENT and adjust_stack
functions.
This adds a benchmark to measure how much slower multiple
assignment is with the correct evaluation order.
This benchmark shows:
* 4-9% decrease for attribute sets
* 14-23% decrease for array member sets
* Basically same speed for local variable sets
Importantly, it shows no significant difference between the popped
(where return value of the multiple assignment is not needed) and
!popped (where return value of the multiple assignment is needed)
cases for attribute and array member sets. This indicates the
previous optimization, which was dropped in the evaluation
order fix and only affected the popped case, is not important to
performance.
Fixes [Bug #4443]
Notes:
Merged: https://github.com/ruby/ruby/pull/4390
Merged-By: jeremyevans <code@jeremyevans.net>
|
|
https://github.com/ruby/pp/commit/a202dd2c9b
|
|
https://github.com/ruby/pp/commit/3ee131ae92
|
|
This gem exposes no executables, and this makes that clearer.
https://github.com/ruby/resolv/commit/8797a9d3ce
|