| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* YJIT: Chain-guard opt_mult overflow
* YJIT: Support regenerating Jo after Mul
|
|
|
|
|
|
|
|
Reproduction script:
```
require "ripper"
10.times do
20_000.times do
Ripper.parse("")
end
puts `ps -o rss= -p #{$$}`
end
```
Before:
```
28032
34432
40704
47232
53632
60032
66432
72832
79232
85632
```
After:
```
21760
21760
21760
21760
21760
21760
21760
21760
21760
21760
```
|
|
https://github.com/ruby/prism/commit/f393d30ce1
|
|
https://github.com/ruby/open3/commit/69f9c49eb4
|
|
https://github.com/ruby/open3/commit/f1d6988f13
|
|
https://github.com/ruby/open3/commit/a4d9fb99de
|
|
https://github.com/ruby/open3/commit/8c06964d12
|
|
|
|
|
|
|
|
|
|
Upgrade the used Ubuntu version from 20.04 (Focal) to 22.04 (Jammy), alignin
with RubyCI "s390x (Ubuntu)" server.
https://rubyci.org/
Note Travis CI supports Ubuntu 22.04 (Jammy).
https://docs.travis-ci.com/user/reference/jammy/
Set `DFLTCC=0` environment variable as a workaround to avoid the test failures
related to zlib in the `make test-all` and `make test-spec`. The failures can
happen with the zlib library applying the patch madler/zlib#410 to enable the
deflate algorithm producing a different compressed byte stream.
|
|
This reverts commit https://github.com/ruby/zlib/commit/9f3b9c470c05 because we will
fix the issue on alternative way.
https://github.com/ruby/zlib/commit/3dfe3f9110
|
|
https://github.com/ruby/prism/commit/d87607b874
|
|
https://github.com/ruby/prism/commit/4c77944dd4
|
|
|
|
https://github.com/ruby/prism/commit/3e44415ca2
|
|
https://github.com/ruby/prism/commit/0c7d9c3c01
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
We have this code that started failing on 3.3.0-dev recently:
```
irb(main):002> require File.join(RbConfig::CONFIG["rubylibdir"], "observer.rb")
/opt/rubies/3.3.0-dev-09-29/lib/ruby/3.3.0+0/bundled_gems.rb:86:in `<': comparison of String with nil failed (ArgumentError)
end + " which #{RUBY_VERSION < SINCE[gem] ? "will be" : "is"} not part of the default gems since Ruby #{SINCE[gem]}"
^^^^^^^^^^
from /opt/rubies/3.3.0-dev-09-29/lib/ruby/3.3.0+0/bundled_gems.rb:86:in `warning?'
from /opt/rubies/3.3.0-dev-09-29/lib/ruby/3.3.0+0/bundled_gems.rb:92:in `block in <module:BUNDLED_GEMS>'
from <internal:/opt/rubies/3.3.0-dev-09-29/lib/ruby/3.3.0+0/rubygems/core_ext/kernel_require.rb>:42:in `block in require'
from <internal:/opt/rubies/3.3.0-dev-09-29/lib/ruby/3.3.0+0/rubygems/core_ext/kernel_require.rb>:39:in `synchronize'
from <internal:/opt/rubies/3.3.0-dev-09-29/lib/ruby/3.3.0+0/rubygems/core_ext/kernel_require.rb>:39:in `require'
from (irb):2:in `<main>'
from <internal:kernel>:187:in `loop'
from /opt/rubies/3.3.0-dev-09-29/lib/ruby/gems/3.3.0+0/gems/irb-1.8.1/exe/irb:9:in `<top (required)>'
from /Users/byroot/.gem/ruby/3.3.0/bin/irb:25:in `load'
from /Users/byroot/.gem/ruby/3.3.0/bin/irb:25:in `<main>'
```
https://github.com/rubygems/rubygems/commit/d67eddb295
|
|
* rb_warn() does not warn if $VERBOSE is nil, the "always" is wrong.
* Talk about $VERBOSE and not -W since $VERBOSE can be changed at runtime.
|
|
|
|
|
|
The example usage for `then` was mistakenly placed next to `yield_self`.
|
|
|
|
|
|
(https://github.com/ruby/ostruct/pull/56)
The OpenStruct documentation clearly state that it shouldn't
be used when performance is expected.
Ruby 3.3 introduce a new category of warnings that is silenced
by default: performance.
The expected use case is to enable this warning when looking
for potential performance issues within an application.
As such I think it would make sense to emit a performance warning
when OpenStruct is used, as it may help pinpoint that a dependency
rely on it, etc.
https://github.com/ruby/ostruct/commit/5826e12db8
Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
|
|
|
