[#101179] Spectre Mitigations — Amel <amel.smajic@...>
Hi there!
5 messages
2020/12/01
[#101694] Ruby 3.0.0 Released — "NARUSE, Yui" <naruse@...>
V2UgYXJlIHBsZWFzZWQgdG8gYW5ub3VuY2UgdGhlIHJlbGVhc2Ugb2YgUnVieSAzLjAuMC4gRnJv
4 messages
2020/12/25
[ruby-core:101362] [Ruby master Feature#17351] Deprecate Random::DEFAULT
From:
matz@...
Date:
2020-12-10 07:04:54 UTC
List:
ruby-core #101362
Issue #17351 has been updated by matz (Yukihiro Matsumoto). OK, accepted. Matz. ---------------------------------------- Feature #17351: Deprecate Random::DEFAULT https://bugs.ruby-lang.org/issues/17351#change-89069 * Author: Eregon (Benoit Daloze) * Status: Open * Priority: Normal * Assignee: matz (Yukihiro Matsumoto) ---------------------------------------- From https://bugs.ruby-lang.org/issues/17322#note-11 I think we should deprecate the `Random::DEFAULT` constant, it doesn't make sense anymore and it's longer than using Random class methods (Random.rand) or Kernel instance methods (#rand). Also, people might expect it to be global. If users want a Random instance they should just use `Random.new`, not assume there is a global instance in Random::DEFAULT, which is actually rather misleading now (Random::DEFAULT is no longer an instance of Random). Also note that JRuby & TruffleRuby use a per-thread instance for Kernel#rand, etc, to avoid contention (otherwise it becomes a huge source of contention when threads run in parallel). Which means on those implementations using Random::DEFAULT was inefficient (extra synchronization). So for all these reasons I think it's time to deprecate `Random::DEFAULT` and then later remove it (in 3.1?). I don't think there is any use case for `Random::DEFAULT`, but happy to hear if there is and there is no trivial replacement. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>