ml.ruby-lang.org
Sign In Sign Up
Manage this list Sign In Sign Up

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview

ruby-core

Thread Start a new thread
Download
Threads by month
  • ----- 2025 -----
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2024 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2023 -----
  • December
  • November
  • October
  • September
  • August
  • July
  • June
  • May
  • April
  • March
  • February
  • January
  • ----- 2022 -----
  • December
  • November
ruby-core@ml.ruby-lang.org

March 2025

  • 1 participants
  • 162 discussions
[ruby-core:121217] [Ruby master Feature#19059] Introduce top level `module TimeoutError` for aggregating various timeout error classes.
by ioquatix (Samuel Williams) 02 Mar '25

02 Mar '25
Issue #19059 has been updated by ioquatix (Samuel Williams). Status changed from Assigned to Closed It is unlikely that Ruby will adopt this, so I am going to close it. ---------------------------------------- Feature #19059: Introduce top level `module TimeoutError` for aggregating various timeout error classes. https://bugs.ruby-lang.org/issues/19059#change-112158 * Author: ioquatix (Samuel Williams) * Status: Closed * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- This proposal was originally part of <https://bugs.ruby-lang.org/issues/18630> but was removed because we could not decide on the name. Introduce the following: ```ruby module TimeoutError end IO::TimeoutError.include(TimeoutError) Regexp::TimeoutError.include(TimeoutError) # Maybe? Timeout::Error.include(TimeoutError) ``` It may be easier for users. This was discussed before with the following conclusion: - Top level `TimeoutError` is available. - Using a module for a `TimeoutError` may not be consistent with other top level `class #{thing}Error`. -- https://bugs.ruby-lang.org/
1 0
0 0
[ruby-core:121207] [Ruby master Bug#21164] Performance Regression using --jit
by purbug28 (puni ru) 01 Mar '25

01 Mar '25
Issue #21164 has been reported by purbug28 (puni ru). ---------------------------------------- Bug #21164: Performance Regression using --jit https://bugs.ruby-lang.org/issues/21164 * Author: purbug28 (puni ru) * Status: Open * ruby -v: ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +PRISM [x86_64-linux] * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN, 3.4: UNKNOWN ---------------------------------------- Ruby 3.4.2 --jit runs slower than no JIT, while Ruby 3.3.7 --jit runs faster. ```ruby # frozen_string_literal: true n = 200000 c = Array.new(n + 1, 0) (1..n).each do |i| a = [] m = 100 (1..m).each do a << i c[i] += 1 a << i / m c[i % m] += 1 end end puts c.sum ``` results of /usr/bin/time ruby 3.4.2 --jit : 1.98user 0.03system 0:02.02elapsed 99%CPU (0avgtext+0avgdata 19692maxresident)k no JIT: 1.77user 0.02system 0:01.80elapsed 99%CPU (0avgtext+0avgdata 18916maxresident)k ruby 3.3.7 --jit : 1.20user 0.05system 0:01.26elapsed 99%CPU (0avgtext+0avgdata 23220maxresident)k no JIT: 1.81user 0.02system 0:01.83elapsed 99%CPU (0avgtext+0avgdata 22952maxresident)k `ruby -v --jit` ``` ruby 3.4.2 (2025-02-15 revision d2930f8e7a) +YJIT +PRISM [x86_64-linux] ``` -- https://bugs.ruby-lang.org/
2 5
0 0
  • ← Newer
  • 1
  • ...
  • 14
  • 15
  • 16
  • 17
  • Older →

HyperKitty Powered by HyperKitty version 1.3.12.