[#114348] [Ruby master Feature#19832] Method#destructive?, UnboundMethod#destructive? — "sawa (Tsuyoshi Sawada) via ruby-core" <ruby-core@...>

Issue #19832 has been reported by sawa (Tsuyoshi Sawada).

15 messages 2023/08/06

[#114365] [Ruby master Bug#19834] Segmentation fault while running in docker — "ramachandran@... (Ramachandran A) via ruby-core" <ruby-core@...>

Issue #19834 has been reported by ramachandran@mallow-tech.com (Ramachandran A).

7 messages 2023/08/09

[#114380] [Ruby master Bug#19837] Concurrent calls to Process.waitpid2 misbehave on Ruby 3.1 & 3.2 — "kjtsanaktsidis (KJ Tsanaktsidis) via ruby-core" <ruby-core@...>

Issue #19837 has been reported by kjtsanaktsidis (KJ Tsanaktsidis).

7 messages 2023/08/11

[#114399] [Ruby master Feature#19839] Need a method to check if two ranges overlap — "shouichi (Shouichi KAMIYA) via ruby-core" <ruby-core@...>

Issue #19839 has been reported by shouichi (Shouichi KAMIYA).

27 messages 2023/08/18

[#114410] [Ruby master Bug#19841] Marshal.dump stack overflow with recursive Time — "segiddins (Samuel Giddins) via ruby-core" <ruby-core@...>

Issue #19841 has been reported by segiddins (Samuel Giddins).

9 messages 2023/08/18

[#114422] [Ruby master Feature#19842] Intorduce M:N threads — "ko1 (Koichi Sasada) via ruby-core" <ruby-core@...>

Issue #19842 has been reported by ko1 (Koichi Sasada).

30 messages 2023/08/21

[#114590] [Ruby master Bug#19857] Eval coverage is reset after each `eval`. — "ioquatix (Samuel Williams) via ruby-core" <ruby-core@...>

Issue #19857 has been reported by ioquatix (Samuel Williams).

21 messages 2023/08/30

[ruby-core:114529] [Ruby master Feature#19843] Promote bigdecimal as bundled gems at Ruby 3.4

From: "yahonda (Yasuo Honda) via ruby-core" <ruby-core@...>
Date: 2023-08-25 08:16:21 UTC
List: ruby-core #114529
Issue #19843 has been updated by yahonda (Yasuo Honda).


It would be appreciate if this decicions is reconsideed because adding the bigdecimal to the gemspec will install the same version, like 3.1.4 as of today, for all users regardless of which Ruby versions are used.

1. The Rails main branch supports Ruby 2.7.0 or higher. 
-Ruby 2.7 installs BigDecimal 2.0.0 as one of the default gems, while Ruby 3.0 installs BigDecimal 3.0.0 as one of the default gems. 
These versions are older than the latest bigdecimal version 3.1.4 from a major and minor version perspective.

2. There are some notable changes from the Rails point of view since BigDecimal 3.1.0.
	a. 	BigDecimal behavior change in 3.1.0
	https://github.com/ruby/bigdecimal/pull/180
	https://github.com/rails/rails/pull/41115

	b. BigDecimal behavior change in master, will be part of 3.1.5
	https://github.com/ruby/bigdecimal/pull/264
	https://github.com/rails/rails/pull/48693

3. Gem users have no way to specify the gem version added via the add_dependency method based on the Ruby version they use.

Here, I'm not saying whether these changes are good or not, but I want to say that some Ruby 2.7/3.0 users would expect BigDecimal 2.0 and 3.0 behavior as the default gem does.

Thanks,

----------------------------------------
Feature #19843: Promote bigdecimal as bundled gems at Ruby 3.4
https://bugs.ruby-lang.org/issues/19843#change-104328

* Author: hsbt (Hiroshi SHIBATA)
* Status: Closed
* Priority: Normal
----------------------------------------
I triaged target list for bundled gems at https://bugs.ruby-lang.org/issues/19351.

After that, I resolved bigdecimal dependency from our test suite at https://github.com/ruby/ruby/commit/3ef6364a988ab24ca7fdbb7d1b6840b2a40f1466

I propose to promote `bigdecimal` as bundled gems at Ruby 3.4.

@mrkn Is it okay? I will add `bigdecimal` to `Gem::BUNDLED_GEMS::SINCE` for Ruby 3.3.0-preview2.





-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 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/ruby-core.ml.ruby-lang.org/

In This Thread