From: "andrykonchin (Andrew Konchin) via ruby-core" <ruby-core@...>
Date: 2023-01-28T14:23:32+00:00
Subject: [ruby-core:112100] [Ruby master Misc#19096] [Question] Time with `-00:00` offset is in UTC

Issue #19096 has been updated by andrykonchin (Andrew Konchin).


@zverok Thank you for pointing at the original ticket.

TBH I was waiting so long for some official confirmation because I haven't found any mentioning that https://bugs.ruby-lang.org/issues/17544 affects not only `Time#strftime` method but also a way how `utc offset` argument (in Time construction methods) is handled. Even [added tests](https://bugs.ruby-lang.org/projects/ruby-master/repository/git/revisions/9ef66ce3fcfee06d628b611dbc22026d7cc72d0e/diff/test/ruby/test_time.rb) don't check this behaviour.


----------------------------------------
Misc #19096: [Question] Time with `-00:00` offset is in UTC
https://bugs.ruby-lang.org/issues/19096#change-101536

* Author: andrykonchin (Andrew Konchin)
* Status: Open
* Priority: Normal
----------------------------------------
It's a bit unexpected but

```ruby
Time.new(2022, 1, 1, 0, 0, 0, "-00:00").utc?
# => true
```

But time with `+00:00` or `0` offset is treated as not UTC time:

```ruby
Time.new(2022, 1, 1, 0, 0, 0, "+00:00").utc? # => false
Time.new(2022, 1, 1, 0, 0, 0, 0).utc? # => false
```

Is it an intentional behaviour? In this case could you please clarify the reason why it works this way?

---

```
ruby -v
ruby 3.1.2p20 (2022-04-12 revision 4491bb740a)
```




-- 
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/