Activity
From 12/26/2022 to 01/01/2023
01/01/2023
-
07:39 PM Bug #14387: Ruby 2.5 を Alpine Linux で実行すると比較的浅めで SystemStackError 例外になる
- Any update on this?
-
05:56 PM Feature #19294 (Open): Enumerator.product works incorrectly with consuming enumerators
- ```ruby
s = StringIO.new('abc')
Enumerator.product([1, 2, 3], s.each_char).to_a
# Expected: => [[1, "a"], [1, "b"], [1, "c"], [2, "a"], [2, "b"], [2, "c"], [3, "a"], [3, "b"], [3, "c"]]
# Actual: => [[1, "a"], [1, "b"], [1, "c"]]
``... -
05:00 PM Revision 0903a251 (git): Make IO#set_encoding with binary external encoding use nil internal encoding
- This was already the behavior when a single `'external:internal'`
encoding specifier string was passed. This makes the behavior
consistent for the case where separate external and internal
encoding specifiers are provided.
While here, ... -
03:07 PM Bug #19293 (Closed): The new Time.new(String) API is nice... but we still need a stricter version of this
- The Ruby 3.2 style `Time.new(String)` API works very well so far, but since the original `Time.new(Integer, Integer, Integer...)` API actually accepts String objects as its arguments, there's one ambiguous case as follows:
`Time.new('20... - 03:04 PM Revision a4e9606d (git): [rubygems/rubygems] Remove stray word in bundle config man page.
- There was an extra word ("with") in this sentence.
https://github.com/rubygems/rubygems/commit/ad3de5126c -
03:02 PM Revision 44b7fd8d (git): [ruby/net-http] Enhanced RDoc for HTTPHeader
- https://github.com/ruby/net-http/commit/6a282eccdd
-
- Confirmed the fix. Thank you, @nobu!
-
08:27 AM Bug #19292 (Closed): Time object's wday, yday, and isdst returns broken value (and so does to_a) when kwarg in: 'UTC' was given
- Applied in changeset commit:git|542e984d82fa25098eb15398d716d907acc52b93.
----------
[Bug #19292] Re-initialize tm when wday or yday is not set -
- https://github.com/ruby/ruby/pull/7051
-
- Implemented in Ruby 3.0
-
- Implemented in Ruby 3.0:
```ruby
Set[1] <=> Set[1, 2]
# => -1
[Set[1], Set[1, 2]].sort
# => [#<Set: {1}>, #<Set: {1, 2}>]
``` -
10:32 AM Feature #3591: Adding Numeric#divisor? (Have working implementation)
- e8c (Viktor Reznov) wrote in #note-20:
> Two solutions:
3rd:
```ruby
def count_digits(n) = n.digits.count { n.modulo(_1).zero? }
```
-
- matz (Yukihiro Matsumoto) wrote in #note-19:
> Is it more useful than `n % m == 0`?
Yes, statement `n .has_divisor? m` (or `m .divisor_of? n`) has 3 parts instead of 5, and gives a direct answer to the question.
The "problem": htt... -
-
- Applied in changeset commit:git|f527a0911d5ff0476152a3e3c9bcd2247ead5636.
----------
[DOC] [Bug #19290] fix formatting -
-
- It is about monkey patching Kernel and seems an internal document.
I don't think it is useful for users.
https://github.com/rubygems/rubygems/pull/6217
On the other hand, RubyGems has the document about extension of `Kernel#requir...
12/31/2022
-
- $ ruby -e "p Time.new(2023, 1, 1, 0, 0, 0, in: 'UTC').wday"
7
$ ruby -e "p Time.new(2023, 1, 1, 0, 0, 0, in: 'UTC').yday"
0
$ ruby -e "p Time.new(2023, 1, 1, 0, 0, 0, in: 'UTC').isdst"
-e:1:in `isdst': isdst is not set yet (Runt... -
06:29 PM Bug #19291 (Closed): Ripper's on_parse_error token has wrong content
- Ruby 3.1
~~~ruby
Ripper::Lexer.new("{a:,aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa\nhelloworld").scan.map(&:tok)
# =>
["{", "a:", ",", "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa", "", "\n", "helloworld"]
~~~
Ruby 3.2.0
~~~ruby
Ripper:... -
06:01 PM Feature #16986: Anonymous Struct literal - > If I have to pick one from either Struct or Data, I'd pick Data. But still don't like the notation proposed.
What about something like:
%t[a: 1, b: 2]
for Struct (can default to frozen/immutable Struct or use %T to create it f... -
07:04 AM Feature #16986: Anonymous Struct literal
- JFYI JavaScript is having a similar proposal which now proposes `#{…}` syntax.
https://github.com/tc39/proposal-record-tuple
`#` is not a comment marker in that language though. -
02:04 AM Feature #16986: Anonymous Struct literal
- If I have to pick one from either Struct or Data, I'd pick Data. But still don't like the notation proposed.
Matz.
-
01:43 AM Feature #16986: Anonymous Struct literal
- In a Ruby 3.2 context, I wonder how this would look in the mindset of the new Data class instead of a struct?
-
02:23 PM Bug #19248: TestGCCompact#test_moving_objects_between_size_pools test failure
- This seems also due to LTO, adding `%global _lto_cflags %{nil}` to ruby.spec, i.e. removing `-flto=auto -ffat-lto-objects` from compilation flag seems to make this test pass.
-
- Looks like adding `%global _lto_cflags %{nil}` to ruby.spec, i.e. removing `-flto=auto -ffat-lto-objects` from compilation flag makes the above rspec-core test pass (note that Fedora ruby is using gcc).
So maybe LTO is doing "somethin... -
12:03 PM Bug #19290: Documentation: "produces:" (introducing terminal output) is wrongly formatted in few places
- ## `gc.c`
problem: formating not consistent with other source files:
source: https://github.com/ruby/ruby/blob/master/gc.c#L14423
Fix:
```
* _produces:_
```
replaced with:
```
* <em>produces:</em>
```
-
- ## `warning.rb`
Problem: The text "produces:" is embedded in formatted text, it should be normal emphasized text.
view here: https://ruby-doc.org/3.2.0/Kernel.html , 2 times after: "If warnings have been disabled"
source:
htt...
12/30/2022
-
11:13 PM Bug #19278: Constructing subclasses of Data with positional arguments
- zverok (Victor Shepelev) wrote in #note-14:
> > Your example didn't demonstrate this difference.
> ...
Sorry, I think you misunderstood. I understand your points, I am just out of steam and don't care to continue the thread anymore.
... -
- > Your example didn't demonstrate this difference.
> ...
It is a pity, after the thread this long.
If you would've cared, you'd maybe spent a few minutes drafting an `initialize` that would work the way you want **and maintained t... -
- zverok (Victor Shepelev) wrote in #note-12:
> > I don't really understand this example. The initialize works the same way whether you use a Struct or not
> ...
Your example didn't demonstrate this difference.
> 2. These promises are... -
- > I don't really understand this example. The initialize works the same way whether you use a Struct or not
It is not.
1. Both 3.2+ `Struct` and `Data` make a promise that **no other class makes** and is **non-trivial to implement*... -
- zverok (Victor Shepelev) wrote in #note-8:
> BTW, note that before 3.2, for structs it was either `keyword_init: false`, or `keyword_init: true`, not both.
> ...
I don't really understand this example. The `initialize` works the sam... -
- @Eregon Ah, yeah, that's true.
Though I saw codebases that did that for aesthetical purposes (all "classes with methods" look the same), or to not confuse some code analysis tools (I haven't checked lately, but I believe YARD at some... -
03:15 PM Bug #19278: Constructing subclasses of Data with positional arguments
- To clarify:
> Also inheriting from a Data class seems kind of an anti/rare pattern.
I meant one should use `Struct.new(...) { ... }` / `Data.define(...) { ... }` and not `class < Struct.new(...)` / `class < Data.define(...)` which ... -
- > I do this all the time with structs. I assumed Data.define would basically just be a read-only Struct.new and that's how I got here.
(Wrote a long theoretical answer, deleted it!)
Wait. I now reread your initial example more atte... -
- Eregon (Benoit Daloze) wrote in #note-3:
> It seems hard to solve to me, without losing the significant advantages that @zverok mentions.
> ...
😅 I do this all the time with structs. I assumed `Data.define` would basically just be a r... -
06:34 PM Bug #19289: RbConfig::CONFIG["STRIP"] should keep `ruby_abi_version` and `ruby_abi_version` should always be part of Ruby
- I'm not sure why ABI version checking was removed for release versions of Ruby. In the development meeting for the feature, it was decided that we'll keep the same behaviour for development and release versions.
> ko1: Will the ABI ve... -
03:41 PM Bug #19289: RbConfig::CONFIG["STRIP"] should keep `ruby_abi_version` and `ruby_abi_version` should always be part of Ruby
- Eregon (Benoit Daloze) wrote in #note-4:
> That said this kind of configuration is IMHO silly, changing it is basically guaranteed to break things, so a better way would be remove such configuration
I think it was always meant to al... -
- vo.x (Vit Ondruch) wrote in #note-3:
> Just FTR, don't forget that `ruby_version` can be arbitrary string:
> ...
Interesting, I think we should define `RbConfig::CONFIG["abi_version"]` (or `"ruby_abi_version"`) if `RbConfig::CONFIG["ruby... -
- Eregon (Benoit Daloze) wrote:
> the value of `rb_abi_version` would just be the same as `RbConfig::CONFIG["ruby_version"]`
Just FTR, don't forget that `ruby_version` can be arbitrary string:
https://github.com/ruby/ruby/blob/90a80... -
- Another possibility would be to have some key in RbConfig::CONFIG which contains `-Wl,-exported_symbol,_ruby_abi_version` or nil,
like https://github.com/redis-rb/redis-client/blob/809bbab767f8e514ccd0d6008116c360435f3026/hiredis-client... -
- Ah, because the export list file is not given to `strip` but directly to CC/CXX:
* https://github.com/redis-rb/redis-client/blob/809bbab767f8e514ccd0d6008116c360435f3026/hiredis-client/ext/redis_client/hiredis/extconf.rb#L59
* https://... -
- From https://github.com/grpc/grpc/pull/31970 and https://github.com/redis-rb/redis-client/issues/58
First, I think we could add `-K rb_abi_version` to `RbConfig::CONFIG["STRIP"]` so it's automatically kept if `RbConfig::CONFIG["STRIP"... -
04:46 PM Bug #19286: What should kwargs' arity be?
- 💡 In case it helps -- regarding the mention of method parameters above -- I've found it easy to forget how method parameters work so wrote up an entire [article](https://www.alchemists.io/articles/ruby_method_parameters_and_arguments) on...
-
- I would guess because `f({a:1,b:2})` used to work before 3.0 and it was passing "one argument", hence arity 1.
Also `def m(*); end` can be called like `m(a:1,b:2)` and that's clearly one argument on the callee side.
So from the caller po... -
05:51 AM Bug #19286: What should kwargs' arity be?
- kwargs are... complicated. Let me first extend the issue with additional versions of the above (I run Ruby 3.1, but from what I know, everything applies to anything >= Ruby 3.0):
```ruby
[1] pry(main)> method(def a(a:, b:); end).arity
=... -
- Hello, guys. It's time for a quick Ruby quiz.
Q: What is this method's arity?
def f(a:, b:)
end
It requires two arguments, hence it should be 2?
Or if we call this method with one argument, the error message says "wrong number o... -
04:38 PM Feature #15778: Expose an API to pry-open the stack frames in Ruby
- I think such feature has a great potential for production use too, especially for error monitoring. For example, both [Rollbar](https://rollbar.com) and [Sentry](https://sentry.io) tries to support local variables capturing with `TracePo...
-
- Also that script creates Ractors even in "linear" mode.
With the fixed script below:
```
2.040496 0.002988 2.043484 ( 2.048731)
```
i.e. it's also quite a bit slower if any Ractor is created.
Script:
```ruby
require 'jso... -
- It would be more fair to `Ractor.make_shareable(data)` first.
But even with that Ractor is slower:
```
no Ractor:
2.748311 0.003002 2.751313 ( 2.763541)
Ractor
9.939530 5.816431 15.755961 ( 4.289792)
```
This high `s... -
10:39 AM Bug #19288 (Closed): Ractor JSON parsing significantly slower than linear parsing
- a simple benchmark:
```ruby
require 'json'
require 'benchmark'
CONCURRENT = 5
RACTORS = true
ELEMENTS = 100_000
data = CONCURRENT.times.map do
ELEMENTS.times.map do
{
rand => rand,
rand => rand,
... -
- Applied in changeset commit:git|90a80eb076429978e720e11fb17a3cbb96de3454.
----------
Fix integer underflow when using HEAP_INIT_SLOTS
There is an integer underflow when the environment variable
RUBY_GC_HEAP_INIT_SLOTS is less than the ... -
- Thank you for reporting this bug. I have a fix here: https://github.com/ruby/ruby/pull/7044
-
- The test added in 90a80eb0 fails if Ruby is verbose, it outputs the
following line to stderr:
RUBY_GC_HEAP_INIT_SLOTS=100 (default value: 10000) -
02:14 PM Feature #19232 (Feedback): add NoMatchingPatternError#matchee
- Do you have any real use case for this?
-
- There is an integer underflow when the environment variable
RUBY_GC_HEAP_INIT_SLOTS is less than the number of slots currently
in the Ruby heap.
[Bug #19284] -
- https://github.com/rubygems/rubygems/commit/7c096a5df8
-
- I should have posted the patch to delegate's own repo. Reposted the same patch to https://github.com/ruby/delegate/pull/16
-
- As reported in #19165, method delegation with *, **, and ... adds some overhead for a method that takes no argument. And current implementation of delegations in forwardable and delegate basically define all methods to take splat paramet...
-
01:05 AM Bug #19285 (Third Party's Issue): (docs.rlo) Split stdlib and core documents
- It seems we merge all of the docs for stdlib and core into one for docs.ruby-lang.org, this creates weirdness like [Kernel](https://docs.ruby-lang.org/en/master/Kernel.html) which includes monkey patches for rubygems for example.
> Ru...
12/29/2022
-
11:38 PM Bug #15072 (Closed): thread.c:4356:5: error: implicit declaration of function ‘ubf_list_atfork’
- Fixed in #15130
-
- @mame https://bugs.ruby-lang.org/issues/19026#note-7 should be a good enough reason on its own IMHO.
And as we have seen with recent simplecov issues, it's always a bad idea to use a version check for checking if a feature is available. -
08:31 AM Bug #19279 (Closed): Allow `Coverage.supported?` to recognize oneshot lines mode
-
- Okay, I merged it. If you think this should be backported you need to ask @nagachika :)
-
02:53 AM Bug #19279: Allow `Coverage.supported?` to recognize oneshot lines mode
- TBH, I don't fully understand the need for `Coverage.supported?`. (I thought `RUBY_VERSION > "3.1"` was good enough as I said in https://bugs.ruby-lang.org/issues/19026#note-6.) So I am not sure of the need for `Coverage.supported?(:ones...
-
- @sam.saffron your hand-maid `Foo` is analogous to `Foo = Data.define(:x)`, right?
Now, can you please show what if somebody wants to inherit your `Foo` to provide:
* argument conversion for `x`
* or, default value for `x`
I belie... -
09:37 PM Bug #19278: Constructing subclasses of Data with positional arguments
- Just going to be a bit more explicit here about the problem for future travelers (I know I am repeating but this is the most succinct way imo to show the issue)...
```ruby
Foo = Data.define :x
class Bar < Foo
def initialize(*args, *... -
- @tenderlove I assure you that I spent a lot of time thinking about possible design decisions, and I believe that while _somewhat unlike_ other classes, the current choice is the best in usability. It is documented (the documentation migh...
-
- It seems hard to solve to me, without losing the significant advantages that @zverok mentions.
Also inheriting from a Data class seems kind of an anti/rare pattern.
One can of course:
```ruby
Foo = Data.define(:x, :y)
def custom... -
- I guess the fact that `new` doesn't behave the same way as `new` on every other class kind of ruins "usability" for me. As an end user, it's not clear why this works:
```ruby
class Foo
def initialize x:, y:
end
end
class B... -
- It is a deliberate and documented design decision: `new` handles unifying positional and keyword args, and `initialize` always [receives keyword args](https://docs.ruby-lang.org/en/master/Data.html#method-c-new).
> Note that Measure#i... -
07:56 PM Bug #19284 (Closed): Integer overflow when using RUBY_GC_HEAP_INIT_SLOTS environment variable
- If you set the environment variable `RUBY_GC_HEAP_INIT_SLOTS` to anything other than `0`, an integer overflow runtime error occurs:
```ruby
RUBY_GC_HEAP_INIT_SLOTS=10000 ruby -e 'puts "hello, world!"'
# => ruby: integer overflow: 36... -
05:40 PM Bug #19270: Constants lookup and a singleton class issue
- It's expected behavior. When you have a singleton class `singleton_class.ancestors` is:
[singleton_class, attached_object_class, ...]
In this case the lookup for starts at `A`, which is `attached_object_class`.
It goes to the ... -
-
11:04 AM Bug #19282: Regex error on ruby 3.2
- This issue is same with https://bugs.ruby-lang.org/issues/19283 and both I made. Would you remove this issue?
- 10:55 AM Bug #19282 (Closed): Regex error on ruby 3.2
- There is an regex error pattern on ruby 3.2.0. This pattern is success on ruby 3.1.3.
Is this a bug? Or, is ruby 3.2.0 correct?
- ruby 3.2.0
```
# ruby -v
ruby 3.2.0 (2022-12-25 revision a528908271) [x86_64-linux]
(byebug) MAX_... -
04:14 PM Misc #19276: It is not possible to reply to emails from redmine
- It looks like the message does eventually go through https://bugs.ruby-lang.org/issues/19274#note-4 , however (when doing the typical reply-all) there is still the error message from google about address not existing.
-
06:42 AM Misc #19276 (Assigned): It is not possible to reply to emails from redmine
- 01:20 PM Revision f430701b (git): [DOC] remove space from inside code span element
-
- The report about arity is correct.
`Data` decouples `.new` and `#initialize` this way:
* `.new` accepts positional and keyword args, and converts positional to keyword, and passes them to `#initialize`
* `#initialize` accepts only ... -
01:21 AM Bug #19280 (Closed): Wrong error message about arity of Data::define.new
- ```
$ ~/work/r/bin/ruby -e 'Data.define(:a, :b).new(1, 2, 3)'
-e:1:in `new': wrong number of arguments (given 3, expected 0..2) (ArgumentError)
Data.define(:a, :b).new(1, 2, 3)
^^^^^^^
from -e:1:in ... -
11:26 AM Bug #19273: [Regexp] regexp does not match expected
- ruby_3_2 a7d467a792c644a7260d6560ea2002fdb8ff6de3 merged revision(s) b726d60c986bf951d13e7a2ab5f5e58f58657b03.
-
- ruby_3_2 5c551ac59f9620901394a46dffda5a1833b9c4b0 merged revision(s) fc03ba50f1ff6c30f7c654f564b4dffbed0844ef.
-
- There is an regex error pattern on ruby 3.2.0. This pattern is success on ruby 3.1.3.
Is this a bug? Or, is ruby 3.2.0 correct?
- ruby 3.2.0
```
# ruby -v
ruby 3.2.0 (2022-12-25 revision a528908271) [x86_64-linux]
(byebug) MA... -
- These are syntax error
~~~ruby
p (1;2),(3),(4)
p (;),(),()
a.b (1;2),(3),(4)
a.b (;),(),()
~~~
I expect it to be syntax ok because the code below is syntax ok.
~~~ruby
p (1),(2;3),(4;5)
p (),(;),(;)
a.b (1),(2;3),(4;5)
a.b ()... -
08:56 AM Bug #18743: Enumerator#next / peek re-use each others stacktraces
- Good evening, @matz. The PR with the bug fix is available now for a few months. Please advise on the next steps.
- 08:23 AM Revision b3d330c3 (git): Coverage.supported? recognizes oneshot_lines mode (#7040)
- This adds oneshot_lines as a mode of coverage that is supported.
-
- Fix [Bug 19273], set correct value to `outer_repeat` on `OP_REPEAT`
(#7035)
---
regexec.c | 2 +-
test/ruby/test_regexp.rb | 5 +++++
2 files changed, 6 insertions(+), 1 deletion(-) -
-
- As @duerst mentioned, we understand the need for (some kind of) package importing, and @shioyama is now working on it. But we are far away from completion.
I personally feel it is a good idea to combine this package with refinements.
...
12/28/2022
-
- Thanks. We will investigate this.
-
- It is no possible to reply to email from about issue update in order to add further comments to the tickets. Is that something that could be turned on? I think it would be user friendly to be able to react directly from mail client, with...
-
08:22 PM Bug #19279: Allow `Coverage.supported?` to recognize oneshot lines mode
- I just created the PR here: https://github.com/ruby/ruby/pull/7040
-
- I basically agree with fixing this - can you link the PR?
The only feedback I have is that `:lines` and `:oneshot_lines` are basically the same from a compatibility POV. I wonder if the flags should actually be `:lines | :oneshot`. Beca... -
- I have a commit to support this that I'd like to contribute as a PR, but am waiting on doing so until the process here plays out. Thanks!
-
- Currently in Ruby 3.2.0, Coverage's new `supported?` method (introduced in https://bugs.ruby-lang.org/issues/19026) does not recognize support for oneshot lines. Given that it is an available mode of coverage, I'm proposing that `Coverag...
-
- I'd expect both of the following subclasses to work, but the subclass that uses positional parameters raises an exception:
```ruby
Foo = Data.define
class Bar < Foo
def initialize foo:
p foo
end
end
class Baz < Foo
... -
06:31 PM Feature #19277: Project-scoped refinements
- I didn't mention this in the original issue because it's not the primary motivation for project configuration here, but a secondary benefit of project configuration is affording a place to opt in to new interpreter features (frozen strin...
-
- Refinements are a great way to isolate patches to the files that rely on them. Nonetheless, I believe the need to explicitly enable refinements in every file that uses them has hindered their adoption. As an inciting example, it’s hard t...
-
05:57 PM Bug #18797 (Open): Third argument to Regexp.new is a bit broken
- Pull request submitted to remove support for the 3rd argument: https://github.com/ruby/ruby/pull/7039
-
- 04:41 PM Bug #19274: Error installing ruby 3.2.0 on RH 8
- ______________________________________________
ruby-core mailing list -- ruby-core@ml.ruby-lang.org
To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/... -
- On 2022-12-28 12:52:41 +0000, aalllop (Alberto Allegue) via ruby-core wrote:
> Issue #19274 has been updated by aalllop (Alberto Allegue).
> ...
+install the devel version?
This is actually distribution specific. For example archlin... -
12:52 PM Bug #19274: Error installing ruby 3.2.0 on RH 8
Sorry, I have posted one of the diferent tests I have done. I have installed first time the 3.2.0 version and the error was the same.
I had installed libyaml-0.1.7-5.el8.x86_64 and now I have installed libyaml-devel-0.1.7-5.el8.x...-
- * You should use the release version of Ruby 3.2.0, not rc1.
* You may need to install `libyaml-devel` or other libyaml library.
-
- When I execute rvm install 3.2.0 the installation fails with the next error:
installing default gems from lib: /var/lib/jenkins/.rvm/rubies/ruby-3.2.0-rc1/lib/ruby/gems/3.2.0+3
abbrev 0.1.0
... -
01:02 PM Bug #19275 (Closed): Bundled gems extensions are not installed with 3.2.0 release tarball
- Bundled gems extensions are not installed with 3.2.0 release tarball when cross building for `aarch64-linux-android` target.
Possibly related to #19271.
Excerpt from build log:
```
2022-12-28T12:39:39.5065133Z linking shared-ob... -
11:44 AM Bug #19273 (Closed): [Regexp] regexp does not match expected
- merged at b726d60c986bf951d13e7a2ab5f5e58f58657b03
-
09:45 AM Bug #19273: [Regexp] regexp does not match expected
- PR [#7035](https://github.com/ruby/ruby/pull/7035) for fixing the bug is created.
-
03:56 AM Bug #19273: [Regexp] regexp does not match expected
- Pattern using `*` quantifier instead of `{0,3}` quantifier matches expactedly.
```
irb(main):027:0> pattern = /(?-mix:(?i-mx:[+-]?0b[01](?:_?[01])*)|(?-mix:[+-]?(?:[1-9]_?(?:\d_?)*)?\d)|(?i-mx:[+-]?0x\h(?:_?\h)*))(?::(?-mix:(?i-mx:[+-]?... -
- This pattern shows a binary|decimal|hexadecimal value splitted by : character.
decimal only and decimal|hexadecimal patterns match expectedly.
decimal only pattern:
```
irb(main):019:0> pattern = /(?-mix:[+-]?(?:[1-9]_?(?:\d_?)... -
03:33 AM Bug #19273: [Regexp] regexp does not match expected
- I performed git bisect and found the first bad commit is [37613fea1657b1a0732501657275bc03e8e0ebc4](https://github.com/ruby/ruby/commit/37613fea1657b1a0732501657275bc03e8e0ebc4).
-
- A regexp pattern does not match expected with Ruby 3.2.
Ruby 3.2
``` ruby
pattern = /(?-mix:(?i-mx:[+-]?0b[01](?:_?[01])*)|(?-mix:[+-]?(?:[1-9]_?(?:\d_?)*)?\d)|(?i-mx:[+-]?0x\h(?:_?\h)*))(?::(?-mix:(?i-mx:[+-]?0b[01](?:_?[01])*)|(... -
- @sawa I didn't mention the solution with numeric arguments because I believe it to be even more cryptic than with named ones.
The reader needs to remember _at all times_ what's the protocol of merge block (`merge` with a block is not... -
07:33 AM Feature #19272: Hash#merge: smarter protocol depending on passed block arity
- Using numbered parameters, we can do slightly better:
```ruby
{apples: 1, oranges: 2}.merge({apples: 3, bananas: 5}){_2 + _3}
```
although I am neutral about the proposal. -
-
06:46 AM Revision 39319216 (git): add debug print for the failure
- http://ci.rvm.jp/results/trunk-gc-asserts@ruby-sp2-docker/4364584
```
1) Failure:
TestObjSpace#test_dump_all [/tmp/ruby/src/trunk-gc-asserts/test/objspace/test_objspace.rb:599]:
number of strings.
<2> expected but was
<3>.
``` -
01:24 AM Bug #19267: Compile fails when enabling YJIT on x64-mingw-ucrt
- Yes, I will disable yjit.
-
-
12/27/2022
-
-
01:34 PM Bug #19243: Windows: Dir.home returns string in wrong encoding
- This is fixed by commit https://github.com/ruby/ruby/commit/d6ce4180a5b4dacbac895c9911031a6df6c61136 in ruby-3.2.0. It should be backported to 3.1 and 3.0.
-
09:45 PM Bug #19271: irb ignores rbs and debug
- YJIT or `RUBY_YJIT_ENABLE=1` doesn't interfere with that process, and I confirmed that this is reproducible without YJIT as @st0012 did. So removing the reference to YJIT from the ticket description, also fixing `ruby -v` as you said.
... -
- I can reproduce this without `IRB`:
```
$ RUBY_YJIT_ENABLE=1 ruby -e "require 'foo'"
Ignoring debug-1.7.1 because its extensions are not built. Try: gem pristine debug --version 1.7.1
Ignoring rbs-2.8.2 because its extensions are not bu... -
04:07 PM Bug #19271: irb ignores rbs and debug
- Impossible to edit the original issue (loads a blank form, looks like a Redmine bug) but `ruby -v` should read:
```
ruby 3.2.0 (2022-12-25 revision a528908271) [arm64-darwin22]
```
I accidentally ran it in the wrong terminal tab when ... -
- Not sure this is a serious issue but when starting IRB this (potentially confusing) message is immediately printed:
```
$ irb
Ignoring debug-1.7.1 because its extensions are not built. Try: gem pristine debug --version 1.7.1
Ignor... -
- > https://github.com/ruby/ruby/blob/master/doc/yjit/yjit.md
> ...
I'm not sure if YJIT supports msys2/ucrt64. If you manually passed `--enable-yjit` to `./configure` (`./configure` does that automatically for supported platforms when rus... -
- Ruby fails to compile with msys2/ucrt64 when enabling yjit.
Error:
``` c
In file included from ./include/ruby/defines.h:72,
from ./include/ruby/ruby.h:25,
from eval_intern.h:4,
... -
- Usage of `Hash#merge` with a "conflict resolution block" is almost always clumsy: due to the fact that the block accepts `|key, old_val, new_val|` arguments, and many trivial usages just somehow sum up old and new keys, the thing that sh...
-
05:05 PM Revision ec7e0829 (git): [ruby/irb] Refactor RubyLex#process_literal_type
- (https://github.com/ruby/irb/pull/350)
Simplify part of regex ``[_a-zA-Z0-9]`` with equivalent shorthand ``\w``.
Replace case-when with match ``$1`` or default value ``?"``, making intention more clear. -
- (https://github.com/ruby/irb/pull/486)
https://github.com/ruby/irb/commit/31cfbeacbb -
12:58 PM Bug #19270 (Closed): Constants lookup and a singleton class issue
- I've noticed that a constant declared in a singleton class may be not visible on an object:
```ruby
class A
def c; C; end
end
a = A.new
klass = (class << a; self; end)
klass.const_set(:C, 1)
a.c
# (irb):2:in `c': uninitial... -
- As far as I understand, name lookup in block is performed related to the context where the block is defined.
The example with `c` (local name) works, because in `instance_eval`, it is implicitly `self.c`. But wouldn't work if you'll sha... -
- I've noticed a confusing behaviour of `#instance_eval` (and `#instance_exec` as well). In some cases it doesn't see constants defined in the object class.
Examples:
```ruby
C = 1
class A
C = 2
end
```
When `#instance_ev... -
12:15 PM Bug #18024: Ractor crashes when connections are closed in multiple Ractors
- I also couldn't reproduce it on m2 mac with both ruby versions 3.0.0 which is reported and 3.2.0 the latest.
I hope it helps.
```
~/src/confirm_bugs.ruby-lang.org/18024 ()
asdf local ruby 3.0.0
~/src/confirm_bugs.ruby-lang.org/180... -
- For both Ruby 3.1.3 and Ruby 3.2.0, building on msys2/ucrt64 fails:
``` c
linking miniruby.exe
/usr/bin/sh: -c: line 1: syntax error near unexpected token `('
/usr/bin/sh: -c: line 1: `/usr/local/ruby/bin/ruby --disable=gems -n -e ... -
- MJIT: Fix JIT code for multiple values in a single case
[Bug #19263]
---
lib/ruby_vm/mjit/compiler.rb | 2 +-
test/ruby/test_mjit.rb | 10 ++++++++++
2 files changed, 11 insertions(+), 1 d... - 01:32 AM Revision db19714b (git): load.c: remove unneeded rb_str_freeze calls
- rb_fstring already resizes and freezes the string, so there's no
need to use rb_str_freeze. -
- https://github.com/ruby/irb/commit/33a5e55ffd
12/26/2022
-
- https://github.com/ruby/net-http/commit/1c8151aaf3
-
- It looks like tool/sync_default_gems.rb is not capable of cherry-picking
commits from ruby/irb. I just executed `tool/sync_default_gems.rb irb`
to fix the sync status.
I'm not sure if what's the cause. It could be related to some diff t... -
- https://github.com/ruby/irb/commit/565eeb3c19
- 09:04 PM Revision 87988756 (git): [ruby/irb] Remove unnecessary warning check on help command
- It's not an intentional behavior of the command and it behaves
differently in different environments. So checking it actually brings
more problem than benefit.
https://github.com/ruby/irb/commit/b3203bc784 - 09:04 PM Revision 148eb05e (git): [ruby/irb] Remove unnecessary test setup
- https://github.com/ruby/irb/commit/cc6e6d26b6
-
- https://github.com/ruby/irb/commit/9cacb5f352
-
- https://github.com/ruby/irb/commit/b7973dd2d2
-
- https://github.com/ruby/irb/commit/f65ec49684
- 08:09 PM Revision 82ca4778 (git): [rubygems/rubygems] Bump rb-sys
- Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.52 to 0.9.53.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.52...v0.9.53)
---
updated-depende... - 07:08 PM Revision f5a035da (git): [rubygems/rubygems] deprecate gem build -C flag
- https://github.com/rubygems/rubygems/commit/fac241d4ef
- 07:08 PM Revision 08f6196b (git): [rubygems/rubygems] add global flag (-C) to change execution directory
- https://github.com/rubygems/rubygems/commit/312fc36711
-
06:52 PM Bug #19266 (Closed): URI::Generic should use URI::RFC3986_PARSER instead of URI::DEFAULT_PARSER
- In June 2014, [`uri/common` was updated][1] to introduce a RFC3986-compliant parser (`URI::RFC3986_PARSER`) as an alternative to the previous RFC2396 parser, and common methods like `URI()` were updated to use that new parser by default....
-
- I think you hadn't read Maxime's very carefully written proposal: https://bugs.ruby-lang.org/issues/18481
-
02:44 PM Misc #19265 (Rejected): please remove rust yjit
- my job is heavily ruby coding and following ruby new versions.(servers and business depend on ruby, like heavy java server clusters)
my one part of job is compile and customizing ruby for use in company.
it's works ok until 3.1.x but 3... - 05:20 PM Revision 28a17436 (git): [rubygems/rubygems] Bump rb-sys in /test/rubygems/test_gem_ext_cargo_builder/custom_name
- Bumps [rb-sys](https://github.com/oxidize-rb/rb-sys) from 0.9.52 to 0.9.53.
- [Release notes](https://github.com/oxidize-rb/rb-sys/releases)
- [Commits](https://github.com/oxidize-rb/rb-sys/compare/v0.9.52...v0.9.53)
---
updated-depende... -
- https://github.com/ruby/irb/commit/998b7a74fa
-
- zverok (Victor Shepelev) wrote in #note-6:
> Intuitively, I don't think so, but I fail to find good logical arguments :)
> ...
Yeah, I think it's uncommon to call `.new` dynamically for core classes so probably no need here.
It would... -
- https://github.com/ruby/ruby/pull/7031
-
- > BTW, should .new be called dynamically too?
Intuitively, I don't think so, but I fail to find good logical arguments :)
(We can, for example, note that `with` is some `Data`-specific and fancy copying/duplication method, and `du... -
- My expectation is it would call `initialize` as well.
I didn't think about that in the review of https://github.com/ruby/ruby/pull/6766, sorry.
So like:
```ruby
class Data
def with(**changes)
self.class.new(**to_h, **changes)
end... -
- In principle, it should call `initialize`. But we will reconsider if any there's any concern (e.g., performance).
Matz.
-
- `Data#with` doesn't call `initialize` nor `initialize_copy`.
It is confirmation request.
```ruby
class P < Data.define(:x, :y)
def initialize_copy(...)
p :initialize_copy
super
end
def initialize(...)
p :in... -
-
- Support `NO_COLOR` (https://no-color.org/) to make parsing output easy.
-
- This is a ticket for backport management.
9f2378959e5c5b5c39c9993f1a84e5304ff113d6 may need to be backported.
https://github.com/ruby/ruby/pull/7023 - 12:02 PM Revision 9f237895 (git): numeric.c: Fix round_half_even for specific values (#7023)
- Handle the integert and the float parts separately in round_half_even
to prevent error occursions in floating point calculation. -
-
- Refine the uses of word "Data", which were often ambiguous. Also,
that word now refers the new class unrelated to `T_DATA`. -
-
-
- I've pushed the fix. Please backport https://github.com/ruby/ruby/commit/fc03ba50f1ff6c30f7c654f564b4dffbed0844ef to ruby_3_2 branch. Other older branches shouldn't need this patch.
-
- ```
$ cat test.rb
def test(a)
case a
when true, false
a
end
end
test(true)
test(true)
$ ruby --mjit-verbose=1 --mjit-wait --mjit-call-threshold=2 test.rb
/tmp/_ruby_mjit_p237606u1.c: In function ‘_mjit0’:
/tmp/_... - 08:40 AM Revision 5e54c57d (git): [DOC] Surface existing MonitorMixin documentation
-
08:34 AM Revision adc29351 (git): EXPR_DOT is set when next token is tANDDOT ("&.") [ci skip]
-
-
-
- [Bug #19263]
- 06:10 AM Revision 39a96b43 (git): Update default gems list at b7ad60a79440f65cf883d3ff9dbdde [ci skip]
-
- from https://github.com/rubygems/rubygems/commit/72fd3dd2096af16d797ad0cd8e0d2a8869e240b3
- 06:09 AM Revision 10c9ce9d (git): bump up to 3.0.5
-
06:09 AM Revision 24c9adca (git): [ruby/openssl] test/openssl/test_pkey.rb: allow failures in test_s_generate_parameters
- Commit https://github.com/ruby/openssl/commit/f2e2a5e5ed8e ("test/openssl/test_pkey.rb: allow failures in
test_s_generate_parameters", 2022-12-23) was completely bogus. The
problem in OpenSSL 3.0.0-3.0.5 is that errors from the callback ... - 06:09 AM Revision cea6951e (git): [ruby/optparse] Add symbolize_names to getopts
- https://github.com/ruby/optparse/commit/3e63d878f8
-
- https://github.com/ruby/optparse/commit/73661899ad
-
- (https://github.com/ruby/net-http/pull/97)
https://github.com/ruby/net-http/commit/768115167a -
- https://github.com/ruby/net-http/commit/b85530e6b8
- 06:09 AM Revision 50e58df0 (git): [ruby/csv] Bump version
- https://github.com/ruby/csv/commit/8606ee83e0
- 06:09 AM Revision 79ad0452 (git): [ruby/strscan] Bump version
- https://github.com/ruby/strscan/commit/3ada12613d
-
- (https://github.com/ruby/fiddle/pull/118)
String#unpack1 is available since Ruby 2.4, and support for older than
Ruby 2.5 was dropped by #85.
Also simplified a common return statement. - 06:09 AM Revision 1dc8c18b (git): [ruby/fiddle] Bump version
- https://github.com/ruby/fiddle/commit/3033266902
-
-
- These tests do not only consume hundreds GiB bytes memory, result in
`rb_bug` when `RUBY_DEBUG` is enabled. -
- * Rewrite Kernel#loop in Ruby
* Use enum_for(:loop) { Float::INFINITY }
Co-authored-by: Ufuk Kayserilioglu <ufuk@paralaus.com>
* Limit the scope to rescue StopIteration
Co-authored-by: Ufuk Kayserilioglu <ufuk@paralaus.com> -
- I postponed enabling them at Ruby 3.3 because CI is always failed.
https://github.com/ruby/ruby/commit/a236661a62dc89173dcdd9e071365929db1201a7
We should track them in this ticket.
-
- https://github.com/ruby/ruby/actions/runs/3778576415/jobs/6423165914
ruby 3.3.0dev (2022-12-25T23:46:59Z master 2a6dbf03a2) [i686-linux-gnu]
```
1)
Literal Regexps handles a lookbehind with ss characters ERROR
RegexpErro... -
- After bumping version, we got the some fails with ruby/spec.
https://github.com/ruby/ruby/actions/runs/3778576412/jobs/6423166914
```
1)
Literal Regexps handles a lookbehind with ss characters ERROR
RegexpError: invalid pa... -
-
- We discussed this again in the DevMeeting-2022-12-15. We agreed to make the following changes after the Ruby 3.2 release. Now that Ruby 3.2 is released, I'm publishing this update and making permission changes on the IRB repository.
###... -
04:19 AM Bug #19262 (Closed): Segmentation fault on RubyVM::AbstractSyntaxTree.node_id_for_backtrace_location
- It seems that `RubyVM::AbstractSyntaxTree.node_id_for_backtrace_location` gives a Segmentation fault if any argument other than `Thread::Backtrace::Location` is given.
repro:
```
$ ruby -e 'RubyVM::AbstractSyntaxTree.node_id_for_b... -
-
- `Data#members` is defined but it is calculated by `self.class.members` (in other words, `#members` is a shorthand for `self.class.members`).
So it is better to remove this method.
```ruby
P = Data.define(:x, :y)
p P.new(1, 2).membe... -
- Tested by another OpenBSD developer and confirmed to significantly
improve things. - 03:08 AM Revision d29096f4 (git): Update default gems list at cd6c7613f31a371326d86de55af159 [ci skip]
-
- Reverts the following commits:
eb8d4d7b5145849325985c00b810b8d75661d86e
edb83dc3a2c374e880e8eb488152872152790e92
d40064d1846b5835dff81e3f168c0c3a6c85e814 -
02:43 AM Revision bb2c3601 (git): Update NEWS.md for 3.3.0 [ci skip]
-
-
-
- Thanks for trying Ruby 3.2 quickly.