| Age | Commit message (Collapse) | Author |
|---|
|
It wasn't clear that the mode also translates "\r" to "\n".
Notes:
Merged: https://github.com/ruby/ruby/pull/6981
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6993
|
|
... and add code to parse the sections of .debug_addr_base and
.debug_rnglists_base.
Notes:
Merged: https://github.com/ruby/ruby/pull/6993
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6993
|
|
... and add VAL_addr value type
Notes:
Merged: https://github.com/ruby/ruby/pull/6993
|
|
clang generates DWARF with the sections
Notes:
Merged: https://github.com/ruby/ruby/pull/6993
|
|
The following script crashes:
```ruby
GC.auto_compact = true
GC.stress = true
class Foo
def initialize
@a = @b = @c = 0
end
def add_ivars
@d = @e = @f = 0
end
end
ary = 1_000.times.map { Foo.new }
ary.each { |f| f.add_ivars }
```
This is because in rb_grow_iv_list, it first calls
rb_ensure_iv_list_size to allocate the buffer (and also unsets the
embed bit) then rb_shape_transition_shape_capa to get the new shape.
However, auto-compact can trigger in rb_shape_transition_shape_capa
which would re-embed the object since it doesn't have the new shape yet.
This causes a crash as the object is now embedded but has a non-embed
shape which would cause the object to have a buffer overrun.
Notes:
Merged: https://github.com/ruby/ruby/pull/6986
|
|
|
|
|
|
|
|
Background: GCC 12 generates DWARF 5 with .debug_rnglists, while rustc
generates DWARF 4 with .debug_ranges.
The previous logic always used .debug_rnglists if there is the section.
However, we need to refer .debug_ranges for DWARF 4.
This change keeps DWARF version of the current compilation unit and use
a proper section depending on the version.
Notes:
Merged: https://github.com/ruby/ruby/pull/6980
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6980
|
|
... and properly support DW_FORM_line_strp.
This is a prepartion to support DWARF 5.
Notes:
Merged: https://github.com/ruby/ruby/pull/6980
|
|
|
|
https://github.com/ruby/optparse/commit/2a1e157ae1
|
|
|
|
Notes:
Merged: https://github.com/ruby/ruby/pull/6988
|
|
[Misc #19250]
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
|
|
|
|
|
|
This reverts commit 89a66f20d8701f30f3d9952ae62a02fdefcd166b.
|
|
|
|
This makes sure the method returns nil for these events, as
described in NEWS, even if the TracePoint could create a binding.
Notes:
Merged: https://github.com/ruby/ruby/pull/6984
Merged-By: jeremyevans <code@jeremyevans.net>
|
|
Adjust call-seq to mention block, and add examples
and explanations.
Notes:
Merged: https://github.com/ruby/ruby/pull/5380
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Implements [Feature #19000]
This commit adds copy with changes functionality for `Data` objects
using a new method `Data#with`.
Since Data objects are immutable, the only way to change them is by
creating a copy. This PR adds a `with` method for `Data` class instances
that optionally takes keyword arguments.
If the `with` method is called with no arguments, the behaviour is the
same as the `Kernel#dup` method, i.e. a new shallow copy is created
with no field values changed.
However, if keyword arguments are supplied to the `with` method, then
the copy is created with the specified field values changed. For
example:
```ruby
Point = Data.define(:x, :y)
point = Point.new(x: 1, y: 2)
point.with(x: 3) # => #<data Point x: 3, y: 2>
```
Passing positional arguments to `with` or passing keyword arguments to
it that do not correspond to any of the members of the Data class will
raise an `ArgumentError`.
Co-authored-by: Alan Wu <XrXr@users.noreply.github.com>
Notes:
Merged-By: k0kubun <takashikkbn@gmail.com>
|
|
cf0b413ef8b794ef6e7436f22fd5a998050dada9
|
|
|
|
https://github.com/ruby/net-http/commit/71bae5c0fe
|
|
https://github.com/ruby/net-http/commit/e4df80f299
|
|
https://github.com/ruby/net-http/commit/df5a554fa8
|
|
* Set up RBS_SKIP_TESTS
Notes:
Merged-By: soutaro <matsumoto@soutaro.com>
|
|
|
|
Surrounding with brackets is just a convention for the bugs tracker
links.
|
|
|
|
Inconsistency pointed out by @mame:
```
>> Enumerator.product([1], [2], [3]).to_a
=> [[1, 2, 3]]
>> Enumerator.product([1], [2]).to_a
=> [[1, 2]]
>> Enumerator.product([1]).to_a
=> [1]
>> Enumerator.product().to_a
=> [nil]
```
Got fixed as follows:
```
>> Enumerator.product([1], [2], [3]).to_a
=> [[1, 2, 3]]
>> Enumerator.product([1], [2]).to_a
=> [[1, 2]]
>> Enumerator.product([1]).to_a
=> [[1]]
>> Enumerator.product().to_a
=> [[]]
```
This was due to the nature of the N-argument funcall in Ruby.
|
|
|
|
|
