Activity
From 10/22/2024 to 10/28/2024
10/28/2024
-
08:38 PM Revision 3c9be02a (git): [ruby/prism] Only read from buffer if `size` is greater than 0
- It looks like we can possibly do an out of bounds read if size is equal
to 0. This commit adds a conditional to ensure size is actually greater
than 0 before looking backwards in the buffer
https://github.com/ruby/prism/commit/2031b626e6 -
02:39 PM Revision 83568a41 (git): Install simplecov for net-imap 0.5.0 test
-
- - Fix filtering by ARGV
- Adjust top library names from gem names
- Skip if no tests found -
02:08 PM Bug #20819 (Open): IO#readline does not process newlines correctly for wide character encodings
- When not performing character conversion, IO#readline only processes newline characters as ASCII when reading paragraphs. However, when character conversion is involved, even when converting between 2 ASCII incompatible encodings, newli...
-
02:05 PM Revision a8f220ed (git): [DOC] Tweaks for Array#uniq (#11949)
-
01:54 PM Feature #20818 (Feedback): Allow passing a block to Hash#store (to update current value)
- I would like to propose a block form for `Hash#store`. In addition to passing a value, it should also be allowed to pass a block.
If passed a block instead of a value, the block is called with the current value or, if unset, the hash's ... -
-
-
- Pass configure options to the generated Makefile as-is.
-
-
-
04:31 AM Revision d09b47dd (git): merge revision(s) 70d20ce473952e3a2e5b0aa4a6884886517ee3cc:
- Update bundled gems list
-
10/27/2024
-
11:44 AM Misc #20781: DevMeeting-2024-11-07
- * [Feature #20811] `warning: in a**b, b may be too big` is really helpful? (mame)
* I think the warning is not useful. Can we remove the warning?
10/26/2024
-
04:32 PM Feature #20815 (Closed): Fetch for nested hash
- Closing because it's a duplicate.
-
- https://github.com/ruby/stringio/commit/ef03f9368d
-
- https://github.com/ruby/stringio/commit/a2aab4721c
-
- In Ruby 2.7 and later, it is the same as `StringValue`.
https://github.com/ruby/stringio/commit/561ea67ea8 -
- I can also repro on macOS. Comparing profiles between 3.2 and 3.3, in both case the overwhelming majority of the time is spent in the thread scheduler.
The one big difference I can see is that 3.2 seem to use `poll` to wait on threads... -
09:50 AM Bug #20816: Potential regression in Ruby 3.3.x (compared with 3.1 and 3.2) regarding fast syscalls and multi-threading.
- Thanks, these numbers are slightly more "expected" than mine (Ubuntu 24.04), especially for 2 threads, but other that that it looks like the "regression" is also visible on MacOS.
For the record I also tested with ruby master (3.4.0 as ... -
- The result on my machine (Apple M2 Pro, 12 processors).
Note that N=5_000_000, a half of your example.
|Threads\Ruby| 3.1.4 | 3.2.5 | 3.3.5 | 3.4.0 |
|-----------:|-------:|-------:|-------:|-------:|
| 1 | 8.818 | 5... - 09:45 AM Revision 519f5591 (git): Update default gems list at caa946f2deba24b26e92aae50441ca [ci skip]
-
09:44 AM Revision caa946f2 (git): Restore ext/json/extconf.rb
-
-
- Prior to 2.7.3, `JSON::Ext::Parser` would only take kwargs.
So if json_pure 2.7.4 is loaded with `json <= 2.7.2` (or stdlib)
it blows up.
Ref: https://github.com/ruby/json/issues/650
Fix: https://github.com/ruby/json/issues/651
https:/... -
- Fix: https://github.com/ruby/json/issues/646
Since both `json` and `json_pure` expose the same files, if the
versions don't match, the native extension may be loaded with Ruby
code that don't match and is incompatible.
By doing the `re... -
- Ref: https://github.com/ruby/json/issues/647
Ref: https://github.com/rubygems/rubygems/pull/6490
Older rubygems are executing `extconf.rb` with a broken `$LOAD_PATH`
causing the `json` gem native extension to be loaded with the stdlib
v... -
- https://github.com/ruby/json/commit/49de571dd8
-
- This actually never worked, because the test was always testing
the ext version from the stdlib, never the pure version nor the
current ext version. -
- https://github.com/ruby/json/commit/7f079b25be
-
- https://github.com/ruby/json/commit/cecf04fdfc
-
- https://github.com/ruby/json/commit/fb25e94aea
-
- Fix: https://github.com/ruby/json/issues/437
Before:
```json
{
"foo": {
},
"bar": [
]
}
```
After:
```json
{
"foo": {},
"bar": []
}
``` -
-
- https://github.com/ruby/json/commit/937c8d2e65
-
- https://github.com/ruby/json/commit/7a3b482013
-
- https://github.com/ruby/json/commit/a48be35825
-
-
- This regressed since 2.7.2.
https://github.com/ruby/json/commit/35407d6635 -
09:44 AM Revision 2c6e3bc7 (git): Raise the correct exception in fast_serialize_string
- * Related to https://github.com/ruby/json/issues/344
-
- * Otherwise the gem always uses the pure-Ruby backend
as it's missing that file and rescuing the LoadError.
https://github.com/ruby/json/commit/1e2809b0b0 -
- Fix: https://github.com/ruby/json/pull/625
Declaring the buffer in a sub block cause bugs on some compilers.
https://github.com/ruby/json/commit/90967c9eb0 -
- Remove `rapidjson` as it's 2x slower most benchmarks, and on
par on a couple of them, so it's not telling us much here.
Configure `Oj` in compat mode so it generate the same JSON
on the `many to_json` benchmark.
```
== Encoding small n... -
09:44 AM Revision 44aef5e8 (git): [ruby/json] Drop compatibility for missing Array#permutation (Ruby <= 1.8.6)
- https://github.com/ruby/json/commit/b02091ed44
Co-authored-by: Jean Boussier <jean.boussier@gmail.com> -
- Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
-
- https://github.com/ruby/json/commit/b240bde402
Co-authored-by: Jean Boussier <jean.boussier@gmail.com> -
- Co-authored-by: Jean Boussier <jean.boussier@gmail.com>
-
- https://github.com/ruby/json/commit/d4968d2e48
-
- https://github.com/ruby/json/commit/42edaf7f17
-
- Profiling revealed that we were spending lots of time growing the buffer.
Buffer operations is definitely something we want to optimize, but for
this specific benchmark what we're interested in is UTF-8 scanning performance.
Each iterat... -
- Since we're looking up the table anyway, we might as well store the
UTF-8 char length in it. For single byte characters that don't need
escaping we store `0`.
This helps on strings with lots of multi-byte characters:
Before:
```
== En... -
- If we assume that even UTF-8 strings are mostly ASCII, we can implement a
fast path for the ASCII parts.
Before:
```
== Encoding mixed utf8 (20012001 bytes)
ruby 3.4.0dev (2024-10-18T15:12:54Z master https://github.com/ruby/json/commit... -
- Closes: https://github.com/ruby/json/pull/512
https://github.com/ruby/json/commit/d882a45d82
Co-Authored-By: lukeg <luke.gru@gmail.com> -
- Fix: https://github.com/ruby/json/issues/438
https://github.com/ruby/json/commit/9dd89eaac8 -
- Fix: https://github.com/ruby/json/issues/534
Only include up to 32 bytes of unparseable the source.
https://github.com/ruby/json/commit/f44995cfb6 -
- https://github.com/ruby/json/commit/09e1df2643
-
- https://github.com/ruby/json/commit/1a9af430d2
-
- Avoid needless hash allocations and such that degrade performance
significantly on micro-benchmarks. -
- Fix: https://github.com/ruby/json/issues/419
-
- Note where we currently stand, what the current bottlencks are
and what could or can't be done.
```
== Encoding small nested array (121 bytes)
ruby 3.3.4 (2024-07-09 revision https://github.com/ruby/json/commit/be1089c8ec) [arm64-darwin... -
09:44 AM Revision 5fa491b4 (git): Normalize lockfile platforms
-
09:44 AM Revision e61bb75a (git): [ruby/strscan] [JRuby] Optimize `scan()`: Remove duplicate `if
- (restLen() < patternsize()) return context.nil;` checks in
`!headonly`.
(https://github.com/ruby/strscan/pull/110)
- before: #109
## Why?
https://github.com/ruby/strscan/blob/d31274f41b7c1e28f23d58cf7bfea03baa818cb7/ext/jruby/org/jrub... -
- unnecessary use of `rb_enc_get()`
(https://github.com/ruby/strscan/pull/108)
- before: #106
## Why?
In `rb_strseq_index()`, the result of `rb_enc_check()` is used.
-
https://github.com/ruby/ruby/blob/6c7209cd3788ceec01e504d99057f9d3b... -
- (https://github.com/ruby/strscan/pull/101)
https://github.com/ruby/strscan/commit/d31274f41b - 09:44 AM Revision e7f06402 (git): Bump version
- 09:44 AM Revision 2ec2051f (git): [ruby/fiddle] Don't use mkmf to generate dummy Makefile
- (https://github.com/ruby/fiddle/pull/155)
GitHub: fix https://github.com/ruby/fiddle/pull/153
mkmf requires fileutils. JRuby doesn't like it.
https://github.com/ruby/fiddle/commit/df4bd21fc3 -
- (https://github.com/ruby/fiddle/pull/157)
The GCC warning puts undefined macro names in double quotes while clang
puts them in single quotes.
https://github.com/ruby/fiddle/commit/7dcb40bccb -
- FFI backend
(https://github.com/ruby/fiddle/pull/156)
* From https://github.com/ruby/reline/issues/766#issuecomment-2422135968
https://github.com/ruby/fiddle/commit/eea9fd0cc4 -
- This seems the case that the recovery works wrongly.
When no syntax error, also the "useless use" warning occurs inside `eval`.
Not in `eval`, the warning is emitted regardless the syntax error. -
06:54 AM Bug #20817: Ruby 3.4.0dev emits `warning: possibly useless use of + in void context` while Ruby 3.3.5 does not
- Related to https://bugs.ruby-lang.org/issues/20736
-
03:47 AM Bug #20817: Ruby 3.4.0dev emits `warning: possibly useless use of + in void context` while Ruby 3.3.5 does not
- Using parse.y parser works as Ruby 3.3.5 does. No warnings emitted.
```
$ RUBYOPT=--parser=parse.y ruby -v
ruby 3.4.0dev (2024-10-25T11:52:32Z master 9c8c140d73) [x86_64-linux]
$ RUBYOPT=--parser=parse.y ruby -w foo.rb
lib/file.rb... -
- Here is the original Rails CI log file.
https://buildkite.com/rails/rails-nightly/builds/1214#0192c57b-b994-43cb-9f48-63b1b41e6f4e/1177-1185
"(eval at lib/file.rb:42):2: warning: possibly useless use of + in void context"
### How ... -
- Ruby 3.4.0dev emits `warning: possibly useless use of + in void context` while Ruby 3.3.5 does not
This issue is based on Rails Action Pack test case against Ruby 3.4.0dev.
Here is the minimum script to reproduce it.
### Steps to ... -
12:46 AM Revision 9838c443 (git): Make builtin init ifdefs consistent
10/25/2024
-
- Ok I'm sorry in advance if this is not really a regression (maybe it's the cost to pay for other improvements) but it still showed as a 30% performance drop in my benchmark so I think it may be worth a look.
For the full story about h... -
07:36 PM Revision 990a5382 (git): Remove useless freelist unlock/lock in gc_ref_update
-
-
02:41 PM Feature #20805: Allow Ractor#send from a signal trap Proc
- It works if you make `shutdown_ractor` a constant:
```ruby
p Process.pid
SHUTDOWN_RACTOR = Ractor.new do
Ractor.recv # Wait for a signal
puts "goodbye"
exit!
end
# Signal trap for SIGTERM
Signal.trap("TERM") do
pu... -
02:40 PM Misc #20013: Travis CI status
- We enabled Travis CI again (enabling the allow_failures) by the PR <https://github.com/ruby/ruby/pull/11948> solving <https://bugs.ruby-lang.org/issues/20810>.
-
- ```ruby
data => user: {profile: {name:}}
p name #=> "Alice"
data => user: {profile: {age:}} #=> NoMatchingPatternKeyError
```
-
01:46 PM Feature #20815: Fetch for nested hash
- I think this might have been suggested in the past as `deep_fetch`. Could it be `dig!` maybe?
-
11:48 AM Feature #20815 (Closed): Fetch for nested hash
- I propose adding a `fetch_nested` method to Ruby’s Hash class, allowing developers to fetch values deeply nested within a hash, with an error raised if any key in the provided path is missing. The method would be similar to dig, but with...
-
- Because of the dynamic feature of Ruby, the optimization on ISeq is very limited.
For instance, elimination of unreachable branch because of a simple always-true/false condition expression, in your example.
> - is there way to disabl... -
11:20 AM Misc #20814 (Feedback): iseq optimizations on constant condition
- ruby 3.4-preview2 seems optimizes out some stuff when building iseq and this may lead to user unexpected behavior when debugging, because some lines just optimized out.
Example:
```ruby
def foo1
if true
nil
else
1
... -
01:32 PM Revision 5c1e4327 (git): Remove rb_ary_new for parser
- rb_ary_new function was not used by the parser and could be removed.
-
- Introduce inline_primary rule to merge the same BNF pattern
-
11:52 AM Revision 9c8c140d (git): Avoid dangling pointer on cygwin
-
07:39 AM Revision f1e92363 (git): [ruby/reline] Add completion_append_character test
- (https://github.com/ruby/reline/pull/773)
https://github.com/ruby/reline/commit/5f5a0aa78c -
- `summary {list-style: none;}` still does not work in Safari 18.
https://github.com/ruby/rdoc/commit/c6a0a6a0d5 -
- Travis CI including the s390x was reenabled on the ruby/ruby master branch by the above PR.
-
- Co-authored-by: Nobuyoshi Nakada <nobu@ruby-lang.org>
- 05:05 AM Revision d089826c (git): .travis.yml: Drop arm32-linux case.
- In the Arm64 Ubuntu jammy (22.04) instance in Travis, we saw the following
error related to the `setarch` failing to run on the 32-bits architecture,
though the linux32 was included in the output of the `setarch --list`.
https://app.tra... -
- There was a report that the Travis CI's long-term infra issue was addressed by
the Travis team on the Ruby Bug ticket 20810.
We especially want to test the s390x (big-endian case) on the pull-request.
Revert ".travis.yml: Drop all the ...
10/24/2024
-
11:12 PM Bug #20804 (Closed): Stop reserving stack ahead-of-time in on Linux
- Applied in changeset commit:git|dcf3add96bd6e117435c568e78be59bb7ecad701.
----------
Delete reserve_stack code
This code was working around a bug in the Linux kernel. It was
previously possible for the kernel to place heap pages in a r... -
-
-
09:07 PM Bug #20813 (Open): Segfault in rgengc_check_relation/RVALUE_WB_UNPROTECTED
- We're seeing this segfault consistently crop up in CI on Ruby 3.3.5 (details below). I'm working on getting a core dump but in the mean time, I was told the console output might be a good starting point to debug.
I thought it might be... -
- removed
(https://github.com/ruby/reline/pull/771)
https://github.com/ruby/reline/commit/e36441652a -
- I sent the following PR to reenable Travis CI including s390x on the rury/ruby master branch.
https://github.com/ruby/ruby/pull/11948
-
- On ruby_3_2, recently all the Travis-CI pipelines are dropped.
https://github.com/ruby/ruby/commit/4873bbd6cc25311fb477bb8fe823d2ea16299717
-
03:08 PM Revision 1634280e (git): Fix shared GC with -DRUBY_DEBUG
- RUBY_DEBUG enables ractor assertions, which sets up some space at the
end of each RVALUE to store the associated ractor ID. We need to make
sure the function that does this is visible to shared GC libraries. -
- include CPPFLAGS, and the correct CFLAGS
-
- I received the following email from Travis support on 19th October.
> Could you please try to trigger a build once again when you are ready and let us know if this issue now appears to be resolved?
> ...
I am starting to test Travis ... - 02:12 PM Revision 78378cae (git): append completion_append_character only when continous completion is … (#764)
- * append completion_append_character only when continous completion is not possible
* refactoring
* remove debug puts -
- wmap_cmp will always return true for dead entries since dead entries have
a Qundef value. When the keys have a hash collision, this may cause the
wrong entry to be returned.
This commit changes wmap_cmp to compare by weakmap_entry point... -
01:26 PM Feature #20812 (Closed): Proposal for Safe Include Method in Ruby
-
01:19 PM Feature #20812: Proposal for Safe Include Method in Ruby
- jeremyevans0 (Jeremy Evans) wrote in #note-1:
> rogerconsul (Roger Consul) wrote:
> ...
Well... After you mentioned it, I realized we were using version 2.7.5 🥲
Error didn't reproduce on newer versions. We can close this thread.
Th... -
- rogerconsul (Roger Consul) wrote:
> The current `include?` method raises an error when passed `nil` as an argument.
Are you sure?
```ruby
# No Error
[1, 2].include?(nil)
[Object.new].include?(nil)
# Error, but due to custom ... -
- # Proposal for Safe Include Method in Ruby
## Description
Add a new method `include_safe?` to Ruby's `Enumerable` module that safely handles nil arguments in inclusion checks.
## Problem Statement
The current `include?` metho... -
- Regarding `**@`, I'm not a big fan because `**` on the caller side is very much syntax a bit like a keyword, and it has the meaning the pass the Hash/expression as keyword arguments and not as a position argument.
Of course you could ha... -
- https://github.com/ruby/zlib/commit/5a02eac37f
-
- Suppress false positive warnings due to a bug in gcc-14 optimizer.
https://github.com/ruby/zlib/commit/eb1cf426c2 -
- Agreed it should just compute it.
It should still be interruptible by Ctrl+C though, but it probably already is. -
- Agreed. Either Ruby can't do it and should raise some sort of error, or just do it even if it uses gigabytes of memory.
That warning isn't helping anyone, and returning `Infinity` is a huge gotcha and totally unexpected. -
- I tried to calculate the largest prime number recently discovered. However, it did not work. I was a bit disappointed.
```
$ ruby -e 'p 2**136279841-1'
-e:1: warning: in a**b, b may be too big
Infinity
```
I know this is not a ... - 02:47 AM Revision 4df0038d (git): Bump actions/checkout in /.github/actions/setup/directories
- Bumps [actions/checkout](https://github.com/actions/checkout) from 4.2.1 to 4.2.2.
- [Release notes](https://github.com/actions/checkout/releases)
- [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
- [Commits](http... - 12:55 AM Revision a24cb8ac (git): [rubygems/rubygems] [SpecFetcher tests] Use >3 character long fake gem name.
- https://github.com/rubygems/rubygems/commit/ce06b8f0d9
- 12:55 AM Revision 5549dd2c (git): [rubygems/rubygems] [SpecFetcher] Change < to <= like it should be.
- https://github.com/rubygems/rubygems/commit/3d5135e69b
-
12:29 AM Revision 0b3d518e (git): [ruby/error_highlight] Rename the `ErrorHighlight::DefaultFormatter` setting to `max_snippet_width` for clarity
- https://github.com/ruby/error_highlight/commit/e13cbd4335
10/23/2024
-
10:36 PM Revision 60c0c324 (git): [ruby/rdoc] Red-based darkfish color scheme
- (https://github.com/ruby/rdoc/pull/1191)
* Cleanup rdoc.css
* Use red as the highlight color
* Use the same red as ruby-lang.org
* Make main section links stand out more
* Remove scrollbar styling
https://github.com/ruby/rdoc/commi... - 08:03 PM Revision 60d84354 (git): [rubygems/rubygems] [SpecFetcher] Avoid unneeded string allocation.
- https://github.com/rubygems/rubygems/commit/1024505d8e
- 08:03 PM Revision ab7c800e (git): [rubygems/rubygems] [SpecFetcher] Bail before calling available_specs()
- https://github.com/rubygems/rubygems/commit/0719921af4
- 08:03 PM Revision 0f5941a5 (git): [rubygems/rubygems] Replace .map{...}.compact with .filter_map {...}
- https://github.com/rubygems/rubygems/commit/18c4ea7d00
- 08:03 PM Revision 65fd8606 (git): [rubygems/rubygems] Add another bail-early condition to suggest_gems_from_name(), with test.
- https://github.com/rubygems/rubygems/commit/7bb7c0ac2d
- 08:03 PM Revision ff749d99 (git): [rubygems/rubygems] Optimize when suggest_gems_from_name finds an exact match.
- https://github.com/rubygems/rubygems/commit/6c67298584
- 08:03 PM Revision fe66eee1 (git): [rubygems/rubygems] Document suggest_gems_from_name()
- https://github.com/rubygems/rubygems/commit/8f9983cc21
- 08:03 PM Revision 35f0b7c8 (git): [rubygems/rubygems] [suggest_gems_from_name] Bail early if the value is guaranteed to be rejected.
- https://github.com/rubygems/rubygems/commit/56262a9384
-
-
-
-
-
-
-
- > However, the s390x builds are successfully running on other branches( ruby_3_3, ruby_3_2) on Travis CI, which were previously experiencing timeouts.
The latest result of ruby_3_3 is a timeout https://app.travis-ci.com/github/ruby/ruby... -
01:08 PM Misc #20810 (Closed): Re-enable s390x CI Builds on Master Branch in Travis CI
- Description: Currently, the Travis CI has been temporarily disabled on the master branch via Pr(https://github.com/ruby/ruby/pull/11509). However, the s390x builds are successfully running on other branches( ruby_3_3, ruby_3_2) on Travis...
-
-
- We got some core dumps in the wild where a PendingBranch had everything
as None, leading to a panic unwrapping in PendingBranch::into_branch().
This happened while compiling a `branchif`.
It seems that the only way this can happen is wh... -
-
- https://github.com/ruby/ruby/pull/11942
-
- I've seen this sort of failures happen in the past, the root cause generally is that there is another test that runs first an create that symbol in a dynamic way: `"abc".to_sym`.
The solution is to use a more unique symbol value to av... -
- [Bug #20803]
`abc` is used a lot across the ruby spec suite, if another test runs before
this spec is loaded and create this symbol dynamically (`"abc".to_sym`)
the spec will fail.
So it's preferable to use a symbol name that is very u... -
-
-
- gcc 14 for aarch64 with `-O3` may emit a false positive warning for a
pointer access of `RB_BUILTIN_TYPE` called from `RB_TYPE_P`. `Qfalse`
shouldn't get there because of `RB_SPECIAL_CONST_P`, but the optimizer
seems to ignore this cond... -
- With `-pipe` option, gcc of Homebrew on macOS results in a mysterious
error.
```
$ command -v gcc-14
/opt/homebrew/bin/gcc-14
$ gcc-14 --version
gcc-14 (Homebrew GCC 14.2.0) 14.2.0
Copyright (C) 2024 Free Software Foundation, Inc.
This... -
-
- https://github.com/rubygems/rubygems/commit/07e7f0bf5e
-
- ### Before
```
$ GEM_HOME=/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/gems/2.6.0/ bundle
Fetching gem metadata from https://rubygems.org/.
Source rubygems repository https://rubygems.org/ or installed locally is ... -
- https://github.com/rubygems/rubygems/commit/ccd7e084a8
-
- It gives better errors.
https://github.com/rubygems/rubygems/commit/bedae080ef -
- https://github.com/rubygems/rubygems/commit/71fd896041
-
- https://github.com/rubygems/rubygems/commit/ad95a1dfaa
-
- https://github.com/rubygems/rubygems/commit/0511d2c08d
-
- https://github.com/rubygems/rubygems/commit/f530f8686d
-
08:52 AM Revision ad853544 (git): Clarify bundler inline’s `install` parameter
-
07:57 AM Feature #15381: Let double splat call `to_h` implicitly
- > I think that would be awesome. If I do `other_method(**model)` and that model is representable as a hash, passing it as keyword arguments is beautiful.
...until you passed it erroneously, and it was never meant to be, and the error ... - 04:07 AM Revision 19747c1c (git): [ruby/ipaddr] Drop support for Ruby 2.3
- https://github.com/ruby/ipaddr/commit/4685fca13d
- 03:31 AM Revision 0de8b533 (git): Bump github/codeql-action from 3.26.13 to 3.27.0
- Bumps [github/codeql-action](https://github.com/github/codeql-action) from 3.26.13 to 3.27.0.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.m... -
03:03 AM Bug #20807: String#gsub fails when called from string subclass with a block passed
- Regexp.last_match and other regexp-related pseudo globals do not work across more than one stack frame. Since you override #gsub, they are set only inside MyString#gsub
You can confirm with this:
```ruby
def test(klass)
p klass
... - 02:48 AM Revision 25adcddc (git): Bump actions/cache in /.github/actions/setup/directories
- Bumps [actions/cache](https://github.com/actions/cache) from 4.1.1 to 4.1.2.
- [Release notes](https://github.com/actions/cache/releases)
- [Changelog](https://github.com/actions/cache/blob/main/RELEASES.md)
- [Commits](https://github.co... -
- https://github.com/ruby/error_highlight/commit/c565340958
-
- https://github.com/ruby/error_highlight/commit/0657bc1afa
-
- https://github.com/ruby/error_highlight/commit/383490a4b4
10/22/2024
-
- commit:a838f980f599d95ccf344157f7074e997af31f48 should have fixed this issue.
-
09:19 PM Bug #20796: Segmentation fault in rubyzip tests with ruby 3.4.0-preview2~659 e7cb70be4e on x86_64-darwin24
- Though this is just a bug report, it's my first contribution to Ruby Core.
I'm excited to know some new words such as off-one-by bug, valgrind, miniruby, OP reports that were unfamiliar to me.
Thanks! -
- Great to hear, thank *you* very much.
-
- https://github.com/rubygems/rubygems/commit/264c61eb8e
-
- > There are certainly backwards compatibility issues from changing `**` from calling `to_hash` to `to_h`.
What kind of backwards compatibility issues exactly? My idea was to call #to_hash and fall back to #to_h, that should ensure no ... -
- There are certainly backwards compatibility issues from changing `**` from calling `to_hash` to `to_h`. I'm sympathetic to the argument that calling `to_h` fits better, as the conversion is explicit and not implicit, but the backwards c...
-
- > I don’t think it can be treated as “explicitly”
The `**` is right there in the code, written out caller-side, you can't get more "explicit" than that.
> ...
No we can't; as you know `+` is a method (I guess that would make `**` a... -
- > `{}.merge(**obj)` => obj is explicitly splatted but conversion is done via #to_hash instead of #to_h. It makes no sense, as many many people have commented through the years.
I don’t think it can be treated as “explicitly” (invoking... -
- `to_{t}` methods are for explicit type conversion, and `to_{type}` methods are for implicit type conversion.
`{}.merge(obj)` => obj is implicitly expected to be Hash, or converted via #to_hash
`{}.merge(obj.to_h)` => obj is explicitl... -
- I believe that the general agreement is that short `to_{t}` methods (`to_s`, `to_i`, `to_h`, `to_a`) have a semantics of “have some {type} representation/can be converted to {type}", while long `to_{type}` ones have a meaning of “are kin...
-
-
-
-
-
-
- Type information in the context for no additional work!
This is the `if (special_object_p(obj)) return obj;` path in
rb_obj_dup() and for Numeric#dup, it's always the identity function. -
- 02:43 PM Revision e288604e (git): [ruby/reline] Use IO's encoding instead of Encoding.default_external
- (https://github.com/ruby/reline/pull/765)
* use IO's encoding
* refactoring
* remove unused encoding params
* (for retriggering CI) remove unused encoding params
https://github.com/ruby/reline/commit/f09772adab -
- In this example, Ripper wrongly concats `"s333\n"` and `"s4444"`.
~~~ruby
require 'ripper'
code1 = '<<HEREDOC1
s1
#{<<HEREDOC2}s333
s22
HEREDOC2
s4444#{55555}
HEREDOC1'
p Ripper.tokenize(code1)
# => ["<<HEREDOC1", "\n", "s... -
- https://github.com/rubygems/rubygems/commit/9548aa6766
-
- https://github.com/rubygems/rubygems/commit/f4d31c0a97
-
- Merged in 7d254e4a2e16dd6275452a2a67b0fcd600cdc990
-
- This code was working around a bug in the Linux kernel. It was
previously possible for the kernel to place heap pages in a region where
the stack was allowed to grow into, and then therefore run out of usable
stack memory before RLIMIT_S... - 04:17 AM Revision 7d254e4a (git): Perform an actual access check in Dir.tmpdir for writability
- At the moment, this code is looking at the stat output to determine if a
temp directory can be written to. However, just because the stat bits
say that a directory is writable, does not make it so; and, likewise,
the operating system may... -
01:51 AM Bug #20716: Different instance_method behavior in Ruby 2.7 and Ruby 3.x
- Yes, thank you for the fix.
-
- The code in question is written by @osyo and committed by @nobu. Just FYI.