[#101179] Spectre Mitigations — Amel <amel.smajic@...>
Hi there!
5 messages
2020/12/01
[#101180] Re: Spectre Mitigations
— Chris Seaton <chris@...>
2020/12/01
I wouldn’t recommend using Ruby to run in-process untrusted code in the first place. Are people doing that?
[#101694] Ruby 3.0.0 Released — "NARUSE, Yui" <naruse@...>
We are pleased to announce the release of Ruby 3.0.0. From 2015 we
4 messages
2020/12/25
[ruby-core:101780] [Ruby master Feature#17485] Keyword argument for timezone in Time.new
From:
nobu@...
Date:
2020-12-28 14:04:11 UTC
List:
ruby-core #101780
Issue #17485 has been reported by nobu (Nobuyoshi Nakada). ---------------------------------------- Feature #17485: Keyword argument for timezone in Time.new https://bugs.ruby-lang.org/issues/17485 * Author: nobu (Nobuyoshi Nakada) * Status: Open * Priority: Normal ---------------------------------------- Currently, `Time.at` and `Time.now` accept a timezone as a keyword argument, but not `Time.new`. This means minor arguments cannot be omitted for `Time.new`. ```ruby Time.new(2021, 1, 1, 0, 0, 0, "+09:00") #=> ok: 2021-01-01 00:00:00 +0900 Time.new(2021, 1, 1, "+09:00") #=> bad: 2021-01-01 09:00:00 +0900 Time.new(2021, 1, "+09:00") #=> bad: 2021-01-09 00:00:00 +0900 Time.new(2021, "+09:00") #=> ArgumentError (mon out of range) ``` Suggest that Time.new should also accept the `in:` timezone option. -- 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>